File management (was: Re: converting projects to kdevelop)

[Falk Brettschneider]

Hi,

Jean-Marc Valin wrote:
> 2) How do I handle files in multiple directories (is
>    there another way than to have 1 project for each?
> 3) How can I deal with the fact that my .cc (not .cpp)
>    are in .../src directories, which the includes are in
>    .../include ?
You can do conventional tricks like these:
1.) The simplest but most terrible way is to make symbolic links in your
KDevelop project directory.
2.) You know, if you try to add files to a KDevelop which are in ./src
and ./include, make will tell you an error message like this:

cd .. \
  && CONFIG_FILES=t1/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating t1/Makefile
make: *** No rule to make target `src/libsrc.a', needed by `t1'.  Stop.
*** Error ***

You see, with a KDevelop-wizard-created Qt or KDE project it's not
possible to do such things. They expect static libs in other
sub-directories.
The only chance is that you create and use a customer project (use the
KDevelop wizard). Then you have to provide the Makefile by yourself but
on this other hand this allows you to use files which are in
sub-directories of your KDevelop project.
Use tmake (http://www.troll.no) to provide your own Makefile. Copy this
tmake-created Makefile to $(YOURPROJECT)/yourproject (Then KDevelop will
find it and is able to call "Build" and "Debug").
Then copy your C++ files for instance in ./src and ./include, start
KDevelop, open the RFV (I reckon Real File View, anyway you will see all
files which are physically here), click the right mouse button what
opens a context menu and choose: Add file to Project.
But remember your Makefile and the KDevelop project file has nothing to
do with each other. They are two different shoes. In the end you have to
nurse two project files: One for KDevelop (to use all its features) and
one (the tmake profile) for tmake (to build the Makefile).

O.K., this sounds more complicated than it is but that's my way of using
KDevelop and it works well. But you're right, I'm still hoping to get
such a flexible IDE like MSVC++ is in the end.

It should be possible:
1.) to add project files whereever they are!
2.) to add project files without make a copy!
3.) to specify where object files, temporary files and output files
should be placed!
4.) to create sub-projects. (For that reason an additional workspace
file is needed, such one like .dsw)


-- 

Ciao,
--Falk