Re: [CMake] Build cmake child project from cmake parent project

On Wed, Feb 19, 2014 at 06:24:44PM -0500, Aaron Boxer wrote: > I have cmake two projects, with project 2 added as a git submodule in > project 1. > > I would like to build project 2 from project 1. > > How can I do this? I tried add_subdirectory, but this is just for adding > source directories.

[CMake] Build cmake child project from cmake parent project

I have cmake two projects, with project 2 added as a git submodule in project 1. I would like to build project 2 from project 1. How can I do this? I tried add_subdirectory, but this is just for adding source directories. I want to use the project 2 cmake files to build it. Thanks! -- Powered

[CMake] Critical Xcode problem with OBJECT libraries

Hi all. I'm using CMake 2.8.12.1 on Linux, MacOSX, and Windows. On my system I need to build libraries in a large number of subdirectories and link them (statically) with various executables (different executables use different libraries). Then I also need to take the content of all those librar

Re: [CMake] Help debug crazy Windows MSVC issue

On Mon, 2014-02-17 at 08:34 -0500, Paul Smith wrote: > On Mon, 2014-02-17 at 10:20 +0100, Hendrk Sattler wrote: > > Visual Studio 10 totally relies on the custom build tool to protect > > itself when run in parallel. It will run the generator as many times > > as the bar.cpp is mentioned in diffe

Re: [CMake] Why does CMake set CMAKE_OSX_SYSROOT using the Xcode generator?

On 02/18/2014 03:02 AM, Kyle Sluder wrote: > But I'm being stymied by CMake, which is insisting on setting > CMAKE_OSX_SYSROOT to my current platform's SDK despite the fact that I'm > using the Xcode generator. It's designed for builds where everything is for a single OS X platform. One would need

Re: [CMake] include_directories(...) versus set_directory_properties(PROPERTIES INCLUDE_DIRECTORIES ...)

That's just the quick brain dump version. If necessary, I can actually look at old commits, or the current code to try to refresh my memory. I think that's needed. Can you do that research into the commits and discussion? Please see the results of my "research" (aka, old commits detective

Re: [CMake] Check header file woos

Is there any reason, why including just this header is not enough? Maybe some required definitions missing? CMake checks includes by compiling a simple program that does nothing. If compilation fails, the header is assumed not to exist. Those CMake flags can be helpful in diagnosing the issue: