Re: New to aap: misc. problems

On Tue, 6 Jul 2004, Rainer Michael Schmid wrote:
> - The add_LIBS option passes the arguments (as it seems) directly. This

Aap is still evolving, don't forget that. It's not been used on every
possible platform yet.

> the -framework flag). But I wonder why the design decision was to
> specify libraries via -l and not in an abstract manner.

Probably because then ther would need to be some (platform x compiler)
-specific way to convert the list of desired libraries to something
suitable for the linker being used.

> - 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

The Qt stuff is mine, and since there is _no_ standard place to look for
Qt (well, I could have chosen /usr/X11R6), this is what you get. Patches
are welcome, of course (to this list) with an exhaustive search of all the
possible default places it could be.

> -- 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).

That's true - since I wrote the Qt stuff to support the KDE module that
never materialized, and in KDE you munge the moc a bit.

> The handling of the moc is also done in a
> non-standard way that can cause problems.

How so?




-------------------------------------------------------
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