Oh, sorry. I meant it survives `hash -r`.
rüdiger.engineering
Christoph Rüdiger
Düsseldorfer Str. 12
45145 Essen
Germany
phone: +49 201 458 478 58
Von: CMake im Auftrag von
"christoph@ruediger.engineering"
Datum: Montag, 29. Januar 2018 um 11:45
An: Don Hinton
Cc: "cmake@cmak
20:48
An: "christoph@ruediger.engineering"
Cc: "cmake@cmake.org"
Betreff: Re: [CMake] CMake detects suspicious compiler
Sounds like it might be a shell cache issue.
https://unix.stackexchange.com/questions/5609/how-do-i-clear-bashs-cache-of-paths-to-executables
On Fri, Jan
Hi,
I’ve one Linux system here, where cmake always detects a C compiler from a
cross-toolchain. Doesn’t sound strange up to now, but the real deal is that the
path to the compiler is totally unknown to the shell. It is not in PATH, CC and
CXX env variables are empty and CMAKE_C_COMPILER and CMA
201 458 478 58
Von: Hendrik Sattler
Datum: Montag, 15. Januar 2018 um 14:47
An: "cmake@cmake.org" , "christoph@ruediger.engineering"
, "cmake@cmake.org"
Betreff: Re: [CMake] Dual use for single source file
Hi,
I also fell into this trap before:
Don't use MAIN_
Hi folks,
we’re using a clang-based tool for co-processing a bunch of our source files.
The benefit is, that it understands the compile_commands.json database and
hence we do not need to pull out the include paths and the compile definitions
by hand. However, CMake does not compile the source f
