Migrating from KDev2 to KDev3

Alexander Dymo cloudtemple at mksat.net
Thu Mar 25 17:00:31 GMT 2004


On Thursday 25 March 2004 15:32, Jens Dagerbo wrote:
> > 2. I "fixed" the above by just using the "Import existing project",
> > pointing it to a fresh CVS checkout of my project dir, and selecting
> > "Generic C++ Application (Automake based)". Things work better now, but
> > there's one problem with .ui files. In Kdevelop2 the generated header
> > and implementation files from a .ui file ended up in the same directory
> > as the rest of the sources, so I've used
> >
> >    #include "GeneratedFromUIHeader.h"
> >
> > in all my code. Now however, these generated headers end up in the
> > target compilation directory (debug for the time being), so I end up
> > with missing include files. I could just add the build directories to my
> > include path of course, but is there a better way?
>
> What you've hit is, IMHO, a bug in the KDE build system.
I'd rather say it's a feature ;) 

> This occurs when sourcedir != builddir and you, from a different directory,
> attempt to include a header which either is or includes a generated header.
>
> The solution / workaround is to use sourcedir == builddir - which is
> available in KDevelop through "Project -> Build Configuration -> 'default'"
The alternative solution would be to use #include <GeneratedFromUIHeader.h>
(with gcc #include "GeneratedFromUIHeader.h" works too) and add
$(top_builddir) to the include path.

-- 
Alexander Dymo
Ukrainian State Maritime Technical University, ICST Department

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



More information about the KDevelop mailing list