Zitat von Mateusz Loskot :
Trying to figure out how to organise targets I got an idea to
configure these sub-libraries as static library targets
(e.g. libgdal_cpl, libgdal_alg, libgdal_gcore, etc.) which
eventually link to single shared library (libgdal.so).
Learning CMake best practices, I stepp
On Mon, Oct 12, 2009 at 12:57 PM, Pau Garcia i Quiles
wrote:
[...]
> What are the advantages of this? Why don't you rename you
> "project.cmake" files to "CMakeLists.txt" and use add_subdirectory on
> those directories? I see no difference :-?
The difference is becase custom code generation rules
> I've grappled with the same problem recently when rewriting the build system
> for the aqsis renderer project. I certainly don't know what's *best*, but I
> did find a solution which somewhat satisfied me. Let's suppose we have two
> individual subdirectories, libA and libB, and we want to comb
> Yeah, this is a pretty good approach. Unfortunately I had difficulty
> with it because I needed to use code generation via
> add_custom_command() to create some of the source files. I couldn't
> seem to get the dependency resolution for the generated files to work
> unless I had the custom comm
On Mon, Oct 12, 2009 at 12:15 PM, Philip Lowman wrote:
> I would do what makes sense in terms of the end user. If those separate
> subdirectories are meant to be separate libraries, then build separate
> libraries. If the source code is scattered across multiple subdirectories
> but is all suppo
[ Ugh, I replied to this as a private message to Mateusz by mistake.
I'm forwarding it to the list as I hope it may be of general interest. Sorry! ]
-- Forwarded message --
From: Chris Foster
Date: Mon, Oct 12, 2009 at 9:18 AM
Subject: Re: [CMake] Targets organisation of complex
On Sun, Oct 11, 2009 at 9:01 PM, Tyler Roscoe wrote:
> On Sun, Oct 11, 2009 at 08:41:27PM +0100, Mateusz Loskot wrote:
> > The sources are organised in large number of subdirectories and
> > sort of logical sub-libraries, but the binary output of compilation
> > is a single library.
> [snip]
> >
On Sun, Oct 11, 2009 at 08:41:27PM +0100, Mateusz Loskot wrote:
> The sources are organised in large number of subdirectories and
> sort of logical sub-libraries, but the binary output of compilation
> is a single library.
[snip]
> It looks like the best portable approach is to walk through the who
Hi,
Me and my friend, we are porting build configuration of quite complex
project (http://trac.osgeo.org/gdal/) from hand-written makefiles (with
partial support autotools) to CMake.
The sources are organised in large number of subdirectories and
sort of logical sub-libraries, but the binary outp
On Sunday 11 October 2009, you wrote:
> Hi everyone,
>
> Thank you for clarifying this matter.
>
> As an end-user of Eclipse and CMake, I feel that the combination of both
> tools is quite powerful (using CMake, I just threw away autotools...) and
> somehow these tools should be well integrated.
>
Alexander Neundorf wrote:
- Create INTERPROCEDURAL_OPTIMIZATION build feature
I stumbled about this one, as it broke our build (we were using the -ipo flag
for compiling, which didn't work anymore).
After setting the new INTERPROCEDURAL_OPTIMIZATION property to TRUE it worked
again.
Is t
Hi everyone,
Thank you for clarifying this matter.
As an end-user of Eclipse and CMake, I feel that the combination of both
tools is quite powerful (using CMake, I just threw away autotools...) and
somehow these tools should be well integrated.
I will post a message on the Eclipse mailing-list a
Hi,
On Friday 09 October 2009, Dixon, Shane wrote:
> I have a blog on linux.com where I was adding CMake recipes so that I could
> have a catalog of CMake recipes to refer back to when doing later projects.
> I figured that this is something probably best kept in the wiki, so I
> added a "Recipes
On Friday 09 October 2009, Hendrik Sattler wrote:
> Zitat von jens persson :
> > I'm trying to convert an old home grown buildsystem based on make to
> > cmake and one of the requisites[1] is that I need to build each
> > executable in two versions, one with debug symbols and one without. I
> > hav
Alexander Neundorf wrote:
On Saturday 10 October 2009, Bill Hoffman wrote:
CMake 2.8.0 RC 3 is now ready for people to try.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 3
- Avoid non-roo
On Saturday 10 October 2009, Bill Hoffman wrote:
> CMake 2.8.0 RC 3 is now ready for people to try.
> You can find the source and binaries here:
> http://www.cmake.org/files/v2.8/.
>
> Here are the changes for the 2.8.0 branch so far:
>
> Changes in CMake 2.8.0 RC 3
...
> - Create INTERPROCEDURAL_O
On Saturday 10 October 2009, Bill Hoffman wrote:
> CMake 2.8.0 RC 3 is now ready for people to try.
> You can find the source and binaries here:
> http://www.cmake.org/files/v2.8/.
>
> Here are the changes for the 2.8.0 branch so far:
>
> Changes in CMake 2.8.0 RC 3
> - Avoid non-root copies of roo
On Sunday 11 October 2009, Eric Noulard wrote:
> 2009/10/11 Romain CHANU :
...
> > Am I correct Bill or do you have any other solutions?
>
> I let Bill answer that one.
Bill is not very involved in the Eclipse stuff, it's mainly Miguel A.
Figueroa-Villanueva, Eric and me.
Alex
__
2009/10/11 Romain CHANU :
> Thank you for your quick reply.
>
> Eclipse should be the one to fix this issue... Do you know if there is any
> request for it in Eclipse development?
Eclipse fixing the issue means:
"someone concerned with this particular problem provide
patch or manpower to do it".
19 matches
Mail list logo
