On 2/21/2013 10:34 AM, James Turner wrote:
I've just setup a SuperBuild using ExternalProject, and am pleasantly
surprised how well it works so far.
I've encountered one issue, which is awkward - I'm basically using
the SuperBuild to automate assembling / updating dependencies for the
final sub-project, which is the real project I normally work on. I
typically work on that project using Xcode and the Xcode generator.
The problem is, if I use -G Xcode for the super build, some parts
fail (and to be honest this is no surprise - amongst the dependencies
is Boost, for example).
So the question, can I safely set things to use a different generator
for a CMake-based ExternalProject, and still have a top-level build
of everything? The documentation for how the generator flag is
handled by ExternalProject_Add, makes me think there might be
something 'magic' happening. (This would mean, for example, the
top-level Makefile called xcodebuild to build the xcodeprojs I
guess)
I didn't yet try this on MSVC, I'm curious what the situation will be
there with the same setup. Is a top-level NMake build with msbuild of
VisualStudio child projects possible?
It should work. I do VS project builds with VS all the time. The
Xcode generator should work as well. It passes the tests for external
project. So, that should be something that should be fixed.
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
[email protected]
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
