> So for this parallel project structure, an upper level cmakelist used to > organize and setup relationship with lib A, B, C right? >
Correct. The top level CMakeLists.txt lets A B and C all build under a single configuration. One more question is, if use the upper level cmake list, lib_B , lib_C can > be invoked directly without import in proj_a? > If you configure the top level project, you can always invoke make on only the B or C targets via "make A" or "make B". However, by having the "project' command in the CMakeLists.txt for proj_b and proj_c, then those can also be treated as fully independent projects of their own, meaning they can either be configured by themselves or as a part of the top-level. - Chuck
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
