Hi, On Fri, Jun 22, 2012 at 6:10 PM, Leif Walsh <[email protected]> wrote:
> Suppose I have two projects, A and B. A builds a shared lib that links > with a static lib in B. > > Sometimes, I want to build and test B by itself. Other times I want to > build A, which requires building B. > > For now, I manually (or with a script) build B, then set an environment > variable to say where the built static lib is, and then build A (which uses > the environment variable). This is...not superb. > > If I wrote A's CMakeLists.txt to have add_subdirectory(B), it would error > when it hit B's project(B). What makes you think that having 2 project() invocations in the same cmake source tree causes a problem for cmake? Or maybe this was a problem in some older versions of cmake, my 2.8.8 here groks a sample with 2 project() calls in a setup as you describe just fine. Andreas
-- 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
