Hello all,
Kitware will be holding a CMake training course on March 18, 2019 in
Lyon, France. This one-day course will cover the best practice for
CMake, CTest, CPack and CDash.
Please visit our website for more information and registration details:
https://training.kitware.fr/browse/204
N
hello community,
During compilation, cmake shows the information message
*Dependee "DependInfo.cmake" is newer than depender "depend.internal".*
to explain why a file needs to be recompiled.
imediately after
* -- Build files have been written to: ./build**
** /usr/bin/cmake -H. -B./buil
Hello,
How are you adding the library? Are you using "-L /path/to/boost/libs
-lboost_foo" syntax when using target_link_libraries? What do you see when
running "otool -L" on the resulting executable? If you still need to run
install_name_tool, I suppose you can do it using a POST_BUILD cmake co
Hi Juan,
I believe BUILD_WITH_INSTALL_RPATH would place the correct RPATH in the
executables. It’s a potentially easier alternative to using the BUILD_RPATH
property for that purpose. However, I think it’s only half of what needs to
happen. The linker still would be unable to find the boost lib
Robert,
We unfortunately can't just modify the boost libraries where they are installed
because our customers need to be able to build our project from source, and
they would need to do the same thing. We could perhaps do something more
radical like copy those libraries into the build tree and
Hello,
so I didn't get a lot of answers, here's a quick POC which only uses
add_subdirectory() / include_guard() for more questions.
/CMakeLists.txt
/app1/CMakeLists.txt
/app2/CMakeLists.txt
/common/CMakeLists.txt
We have app1 depending on common, and app2 depending on common.
All 3 projects are
