non-kdevprj project

[jbb]

Hi,

Doesn't Project->Generate Project File do this?

It creates a custom kdevelop project based on the directory you point it at. 
It doesn't parse the makefiles but it should be sufficient for a great many 
projects. Or are you thinking of something else?

jbb

On Sun, 01 Jul 2001 10:43, you wrote:
> 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 Automake.am and
> configure.in independance from Kdevelop, like
>
> [dir/subdir/Makefile.am]
> ...
> kdevprj = false
>
> so, when UpdateMakefileam is called for the project that Makefile.am
> remains untouched.
>
> In this manner we can have mixed Automake.am (kdevprj managed or
> untouched)... another time in this case, the Automake.am contained in
> subdirs with Automake.am 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... /?
>
> bye
> Lore
>
> -
> to unsubscribe from this list send an email to
> kdevelop-devel-request at kdevelop.org with the following body: unsubscribe
> »your-email-address«

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