[CMake] Re: Out of source build and KDevelop

[Andrew Maclean]

I use a similar setup to Andy but keep stable common utilities in a
different tree containing just the source.
I have a folder for utilities.
Then in the main project I will have subprojects that compile libraries from
utilities. These are then linked into the main project.
i.e.

/utilities/gps - would contain just source files.
X/Job1/gpsPrj - would be a project that builds a library from /utilities/gps
X/Job1/MainPrj - would be the main project that also links in files from
X/Job1/gps and any other common libraries.
Also X/Job1/ will contain other subprojects of common routines to that
project.

This has the advantage that if bugs are found they only need to be fixed in
one set of source code.



Andrew


-----Original Message-----
From: Alexander Neundorf [mailto:a.neundorf-work at gmx.net] 
Sent: Thursday, 21 October 2004 07:32
To: Andy Cedilnik
Cc: cmake at www.cmake.org
Subject: Re: [CMake] Re: Out of source build and KDevelop

> Hi Alex, 
>  
... 
> I would say your code organization may be wrong too, if you are having 
> the following scenario: 
>  
>   /p1/PROJECT(p1) 
>   /p2/PROJECT(p2) 
>   /src 
>  
> and now you use the code from src in p1 and p2. You should really build 
> a library from the common things and then link it in p1 and p2. 
 
Well, I know the directory setup is kind of strange. But in my common/ 
directory exist source files, and there I don't know in which way they 
might be required (x86, arm-elf, ppc-eabi, with debug, no debug, all 
source files, only some of them, ...). This would result in a big number 
of libraries, with more or less the same names but different behaviour, 
it would be hard to oversee. So building real libraries there currently 
doesn't really make sense for me.  
 
Bye 
Alex 
 

-- 
GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++