Migrating from KDev2 to KDev3

[Jens Dagerbo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

[snip]

I have no idea about the migration issues, so I skipped that.

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

http://bugs.kde.org/show_bug.cgi?id=76277

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

In general, switching back and forth between 'default' and other build 
configurations creates a lot of problems and is not recommended when the 
project is already configured.


jd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAYt+E6meJzsUuplQRAuc3AJ0QGRsoycyMpjQt4dL96kg13PQE0QCgg2/b
cvu5RrE2brIlvIhdbmuw2Nk=
=eEmI
-----END PGP SIGNATURE-----

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