New to aap: misc. problems

Rainer Michael Schmid <[email protected]> Tue, 6 Jul 2004 15:50:47 +0200
Newsgroups gmane.comp.tools.aap.user
Message-ID <[email protected]>
Hi,

I was looking for some time for a nice build tool -- I never got jam 
working properly, ant looks IMO awful and I ended using cmake. But then 
I found aap and from the documentation it looks great and I want to 
start using it.

However, when I did my first experiments with aap I ran into a lot of 
problems and I start wondering if they are only beginner's problem or 
if aap is not as stable yet.

I use aap 1.065 on a Mac running Panther. Here are some problems I 
encountered:

- Building a static library with :lib worked fine for a project with 
pure C files (ar is run and the library works fine). However, I am 
struggling to get the same thing work for a C++ project: when I first 
try to build it, the object files are compiled just fine. But when it 
comes to building the library it tries to do this with g++ and it 
fails. If I start aap again, no source files need to be compiled and it 
tries to build the library with ar and it succeeds. Haven't found a way 
to tell aap to do it right the first time.

- I tried to build a C++ program and aap tried to link it with gcc 
instead of g++. I had to add a {var_LD=$CXX} option to the :program 
rule.

- The add_LIBS option passes the arguments (as it seems) directly. This 
in my case nice, since I need to specify not only "normal" libraries 
(with the -l flag), but also some frameworks to link against (done with 
the -framework flag). But I wonder why the design decision was to 
specify libraries via -l and not in an abstract manner.

- I took a look at the source code of the Qt module and it seems that a 
lot of special things are hardcoded (I haven't tried it yet, but that 
will come soon). E.g. the default for the directory of the Qt 
installation is /usr/local/qt-3.2 (i.e. even ther version is hardcoded 
-- I believe one could try a bit harder to find the right Qt 
installation). The generated .cpp file from a .ui file is modified in a 
strange way (some KDE stuff is done, so you probably can't use it for a 
Qt only project). The handling of the moc is also done in a 
non-standard way that can cause problems.

All in all, I lost a bit the confidence in aap and I am wondering if 
I'm doing something wrong...

Rainer



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com