[CMake] Re: Out of source build and KDevelop

[Bill Hoffman]

OK, I see. So, I guess you will set the source
dir to the top of the entire project, and the binary or build dir
to the actual sub directory.  So, it can access source files from
the entire project, but will still only build the sub project.
The limitation is that every source file in kdevelop has to be relative
to a single source directory.

Sounds good to me.

-Bill


At 09:15 AM 10/20/2004, Alexander Neundorf wrote:
>> OK, you lost me.   Why do you need the top level? 
>> Seems to me that each sub-project should be completely self contained. 
>> If you did not have the parent directories it would work fine, so 
>> why when it has a parent does it need it? 
>>  
>> -Bill 
> 
>I have a source tree which looks like this: 
> 
>src/ 
>src/common/ 
>src/myapp/build-release/ 
>src/myapp/build-debug/ 
>src/anotherapp/build-release/ 
>src/anotherapp/build-debug/ 
> 
>with source files used by both myapp and anotherapp located in src/common/.
>IOW in 
>src/common/ there is no library built, but the source files are used
>directly (since 
>the different builds can be for different target architectures, different
>compile 
>switches etc.). 
>So the projects I'd like to load in kdevelop should originate from the 
>CMakeLists.txt in src/XXXapp/build-XXX/. So I can insert PROJECT() there, no
>
>problem. But since they use source files from src/common/ they should use as
>
>kdevelop project dir src/, i.e. the GetHomeDirectory() and not the cmake
>project 
>source directory (you know, the issue with the relative paths in the
>filelist file). 
> 
>Bye 
>Alex 
> 
>
>-- 
>GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
>+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++