Notes |
|
(0037159)
|
Brad King
|
2014-11-06 12:50
|
|
The variable is called CMAKE_EXE_LINKER_FLAGS. This works for me:
$ cat toolchain.cmake
set(CMAKE_SYSTEM_NAME "Linux")
set(CMAKE_C_COMPILER /usr/bin/cc)
set(CMAKE_C_FLAGS "-fPIE -fsanitize=thread" CACHE STRING "thread cflags")
set(CMAKE_EXE_LINKER_FLAGS "-pie" CACHE STRING "thread ldflags") |
|
|
(0037308)
|
Hinterwaeldler
|
2014-11-27 21:12
|
|
Within my cmake update the same thing happens close to the described problem above, but happens only on a deploy machine (both debian testing with cmake 3.0.2)
The difference: I use the exe linker flag but the result seems to be the same (as described form brad king)
As this has not been seen on the developer machine yet i played around a little bit with cmake call and make call.
No real solution so far, but at leas a workaround, which seems to work:
1. Trigger the cmake call
2. Touch the Toolchain-file
3. Trigger the make
One line call:
rm -rf build ; mkdir build ; cd build ; cmake -DCMAKE_TOOLCHAIN_FILE=../Toolchain-file.cmake .. ; touch ../Toolchain-file.cmake ; make VERBOSE=1 # to see if the flags are appended correctly
btw. i've appended appended a few message logouts to determine the current flags. Every of them looks like expected, but the links.txt does not contain any of the assinged values |
|
|
(0037468)
|
Brad King
|
2014-12-16 10:11
|
|
The solution in 0014066 should address this too.
|
|
|
(0038701)
|
Robert Maynard
|
2015-05-04 09:05
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|