Hi Cmakers, I'm new to CMake and because every new technology is a bit tricky at first, I hope some of you can give me a hint with the following build scenario.
Operating System: Windows There are three directories on the same filesystem hierarchy. - Include-directory - Lib-directory - Subversion-workingcopy The workingcopy contains around 80 applications and like 900 shared libraries and all of those applications can make use of all shared libraries and form together one application suite. What I'd like to accomplish are the following two scenarios combined in one CMake configuration (if possible): 1) Build the complete application suite with automatic dependency resolving. For this scenario I would think that I put a CmakeLists.txt to every folder hierarchy in the workingcopy and add all the necessary folders with add_subdirectory(). Because of the many shared libraries and the somewhat complex folder-hierarchy I'm not that sure about how to manage the dependencies (probably find_package()) but this should not be the question now. The header files, libs and the binaries should be stored in the Include-Directory, Lib-Directory and a binary directory on the same level like the other two directories. 2) Build a shared library or application on it's own without dependency checking. Every shared library and every application is an "independent" project. When building one of these projects the Include-Directory and the Lib-Directory should be used when compiling and linking but if a dependency is missing or a lib file is out of date this should result in a build error in this scenario and the developer has to take care of this situation by himself. The created binaries and libs should be stored in a subdirectory of the corresponding project. So I've got an idea about how to solve 1) but I have no idea how to solve 2) especially in combination with 1). regards Tim
-- 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://www.cmake.org/mailman/listinfo/cmake
