Hi all,
we are trying to re-design the build system of an existing complex project
using cmake.
We have a source tree such this (it is only an example to help explaining
the problem)
.
└── libs
├── CMakeLists.txt
├── libA
│ ├── CMakeLists.txt
│ ├── include
│ │ └── libA.h
│ └── source
│ └── libA.cpp
└── libB
├── CMakeLists.txt
├── include
│ └── libB.h
└── source
└── libB.cpp
The tree contains libraries and executables and many of them have some
dependencies to be
satisfied. We wrote a CMakeLists.txt file on top of the hyerarchy which
repetitively uses the
add_directory directive to build every project under it. This solution
seems to work well
until a project needs another one to be built; in other words, we did not
find out how to deal
with dependencies. Looking at the tree above, we can compile libA but we
cannot compile libB without
installing libA because the latter needs it. What's the right and easy way
to make a target globally
available or at least available for projects on the same level?
Thanks,
Gabriele
--
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:
https://cmake.org/mailman/listinfo/cmake
