project loading

Bernd Gehrmann bernd at physik.hu-berlin.de
Sat Apr 28 13:07:23 UTC 2001


I've sanitized the project loading a bit now. If you
still have any 'old' projects, just delete the gideonprj
in them and import them again. This will create a
foo.kdevelop file which can be loaded. 

The kapp, kpartapp and kpartplugin templates automatically 
create project files. Unfortunately, there is a little
bootstrapping problem with them: The project management
supports kde's hack to automatically create a list of
the directories below the toplevel one (so if applications
are added in kdebase e.g., they are automatically picked
up without adding them to Makefile.am). This list is
created by make -f Makefile.cvs as a file subdirs. 

In summary, the project management only works after
make -f Makefile.cvs. One could let the application 
wizard do this command automatically, but then the
result project could not easily imported into a cvs
repository (because the created files do not belong
there). Any good suggestions are welcome :-)

Bernd.


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



More information about the KDevelop-devel mailing list