Hello,
The snippet:
set(SUITE_DIR /home/../abc)
list(APPEND TEST_LSIT
test_a001)
foreach(test ${TEST_LIST})
message(${test})
string(CONCAT TEST_CMAKE "${SUITE_DIR}/" "${test}/test.cmake")
message(${TEST_CMAKE})
endforeach()
Output:
test_a001
/home/.../abc/test_a001
This is my CMakeLists.txt which is successfully building a shared library, I
just wanted to confirm if it's the right way and it:
cmake_minimum_required(VERSION 3.6)
project(main)
include_directories(
${CMAKE_CURRENT_SOURCE_DIR}/include
${CMAKE_CURRENT_SOURCE_DIR}/build/deps/ya
Hi All,
I'm attempting to replace our use of git submodules with FetchContent flows
instead so we can pull pre-built packages if they already exist instead of
buildings locally.
However, I need to support a flow similar to Git submodules where
developers can edit a submodule and then rebuild the
> Is there a way for me to tell CMake what source files my command relies on so
> it knows when it needs to do a reconfiguration?
CMAKE_CONFIGURE_DEPENDS can do that.
https://cmake.org/cmake/help/latest/prop_dir/CMAKE_CONFIGURE_DEPENDS.html
--
Powered by www.kitware.com
Please keep messages
Hi All,
I'm using execute_process to generate sources and additional CMakeLists.txt
file that then get included in the build. Is there a way for me to tell
CMake what source files my command relies on so it knows when it needs to
do a reconfiguration? For instance, if I touch the python script tha
I am proud to announce the third CMake 3.15 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.15
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.15/release/3.15.html
Some of the more significan
Hello,
I was wondering if there was a way to extract the dependencies/build
order for a target? I know you can create graphs of the dependicies
using graphviz but what I really want is just a list of files in the
build order (whatever order the files would be built in if the build
was serial).
I
Hi Eric,
> Am 27.06.2019 um 13:06 schrieb Eric Doenges :
>
> I can't help you with your other issues, but I believe the solution to this
> problem is to specify "BUILD_ALWAYS TRUE" in your ExternalProject_Add. From
> the documentation for ExternalProject_Add:
> Enabling this option forces the b
thanks for the anwer
quite not... I'm using cmake 3.14.2 (so, far away from 3.6) and have a
look, in main.cpp, there is #include :
$ find /usr/include/ -name filesystem
/usr/include/c++/5/experimental/filesystem
/usr/include/c++/7/experimental/filesystem
/usr/include/c++/8/filesystem
/usr/
Am 26.06.19 um 15:53 schrieb Torsten Robitzki:
A third issue that I have is, that changes to the CMakeLists.txt files in the
Project are not reflected by the super build. If I make a change to one of the
CMake files under ${CMAKE_CURRENT_LIST_DIR}/source, I usually have to delete
the whole bu
10 matches
Mail list logo