[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 140839] project import asking if it should add all sourcefiles
From:       "Jörg" "Rüppel" <joerg () sharky-x ! de>
Date:       2007-01-29 16:55:58
Message-ID: 20070129165558.3609.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=140839         




------- Additional Comments From joerg sharky-x de  2007-01-29 17:55 -------
> I don't see your problem, for custom makefile projects all kdevelop cares >about is a list of \
> files belonging to the project. I don't see why it is a >problem to import your whole project \
> at once. 

Because kdevelop's files are in my project root then. I can move them into the proper \
subdirectory manually and adjust all the filepathes, but I don't want to.

> Also I don't know a single buildsystem that doesn't spread its >buildsystem-files (i.e. .pro, \
> Makefile.am, CMakeLists.txt) over the various >parts of the project. You don't really want a \
> project as big as kdevelop or >kdelibs to have only 1 buildsystem file. 

I am using QMake (which I can't import at all atm), and it works perfectly. You can put \
relative file pathes into QMake projects (this is what KDevelop did a few years ago when I \
created the project), so that the .pro files are in a directory tree parallel to the source \
tree. CMake can do that, too.

> Last but not least: To get the populate-box again you can just remove the >kdevelop.filelist \
> file from your disk after closing the project. Then when >re-opening it kdevelop will ask you \
> wether it should populate the project.

Good to know. Thanks.

Anyhow, the sidebar file browser in KDevelop allows to add files to the project when right \
clicking them. Adding that feature to directories so that it adds files recursively (and with \
relative pathes wrt to the project files) would be perfect.


[prev in list] [next in list] [prev in thread] [next in thread]