Juergen raises a very important point. 

KDevelop1-4 currently must try to comply with the KDE automake/autoconf
scheme as close as possible. The concept of "per file" compiler flags
or "per directory" compiler, linker, makefile flags does not exist
since the concept of a file is unknown. 

VC6 otoh, does not use makefiles until when they get exported. This is
what KDevelop should do in the long run. Note that it is impossible as
of now. KDevelop should be able to generate KDE compliant Makefile.am
and configure.in.in's from a project not the other way around.
Otherwise we need to maintain a minimum of 4 syntax parsers for make,
m4, sh and perl.

VC6 is crap in almost all other respects. This they got right. An IDE
needs to take care of the project management which includes the
dependencies.

Roland



=====
--
Roland Krause
In the garage of life there are mechanics and 
there are drivers. Mechanics wanted!

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/

-
to unsubscribe from this list send an email to kdevelop-request@kdevelop.org with the following body:
unsubscribe »your-email-address«