non-kdevprj project

Lorenzo Delana ldelana at
Sat Jun 30 22:43:09 UTC 2001

Why not add the possibility of import existing project that uses 
auto{conf,make} utilities... like entire kdelibs into kdevelop to let you see 
all the code clicking on the classes tree ?

For example we can have an entry in Project/Import existing project. The only 
addition to made into kdevelop is to notify the and 
independance from Kdevelop, like

kdevprj = false

so, when UpdateMakefileam is called for the project that remains 

In this manner we can have mixed (kdevprj managed or 
untouched)... another time in this case, the contained in subdirs 
with that are kdevprj=false remains untouched.... I think so.

This hint came to me when I think to have the power of KDevelop classes 
browser and other functionally to browser an external source-tree.

PS. now, there is some method to import an auto{conf,make} capable project 
into kdevelop, without using Project/import existing files... /?


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

More information about the KDevelop-devel mailing list