#7 Inconsistent naming of static libraries for gcc
Hi all,
I am currently in the process of converting a complex
multi-platform, multi-language (C and Java) project
from Make/NMAKE to Ant.
The build uses a number of archives/static libraries.
When I specify a name, like, for example, "utility" in
the outfile attribute of the cc task, I get a file
"utility.a". So far, so good.
When I use a library by specifying the same name in the
libs attribute of the libset element, it gets passed
with the -l flag, which will cause gcc to look for
"libutility.a" instead of "utility.a".
Is this programmed in an inconsistent way or am I using
any of the attributes in the wrong way?
Working around this problem in the build.xml is easily
possible, but it gets messy because the workaround must
only be applied for platforms using gcc.
And in fact, messy workarounds like that are the reason
why we are switching to Ant.
Any help is appreciated!
Thanks for creating cpptasks, by the way! Great Job!
Mirko Raner
Software Engineer
PTSC
San Diego, CA
