Carbide: linker error. Too many files?

[mikfi]

Hello guys,

I am compiling with Carbide a project which has about 400 files between headers and source.
When I’ve included all the files, they would compile but not link:
Error: command line is too long.

Then I’ve flattered the directories structure so to have a shorter command line to give to the linker.
It looks like it had some effects, but now I get another – I believe related – problem:
the linker doesn’t find the symbols.

Example:
file1.c: extern int xxx;
file2.c int xxx = 1;

Error:
undefined reference to xxx, resource: file1.c

file2.c it is in the command line given to the linker but it looks like the linker doesn’t care.

Question: does the linker has as well a limitation about the number of files that can be included?

Any idea about how to solve the problem?

Thanks in advance,
Mik

[mpinsonneault]

Mik,

What happens if you build it from the command line with bldmake and abld?

Regards,

Matt P.

[mikfi]

Hi,

from the command line I get errors that Carbide wouldn’t catch/complain about.
Like:
Trace.h:97: badly punctuated parameter list in `#define'

which is:
#define NEW_TRACE( uComponent, eLevel, ... ) \
Trace( uComponent, eLevel, __VA_ARGS__ )


Please note : the same project with much less files (about 80) and with Trace.h included, compiled, linked and run perfectly Carbide and N80.
I may be wrong but I think it is a linker problem.... similar to this one:
http://discussion.forum.nokia.com/fo...ad.php?t=91657

Hoping for suggestions,
Mik

[mikfi]

Problem solved:
I've moved to ARM compiler and everything compile & links nicely.

Mik

[mpinsonneault]

Interesting. So this only happens with GCCE? Or does it happen with WINSCW as well?

Regards,

Matt P.