[CMake] CMake (cmake-gui) silently crashes on Windows 10

After months of working correctly I've found that running CMake in GUI form on Windows 10 suddenly began silently crashing on every launch. It does not appear to be the fault of a recent Windows update given an associate of mine has experienced the same issue in an older version of Windows 10. I i

Re: [CMake] relative path to toolchain does not work

Is this with a clean build directory? The toolchain file is ignored once CMake has run and has done compiler detection. On Wed, Jul 17, 2019 at 11:29 AM hex wrote: > > I specified my toolchain like so: > > 1cmake -DCMAKE_TOOLCHAIN_FILE=myToolchain.cmake .. > > and created a toolchain file in proj

[CMake] [ANNOUNCE] CMake 3.15.0 available for download

I am happy to announce that CMake 3.15.0 is now available for download at: 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 mor

[CMake] relative path to toolchain does not work

I specified my toolchain like so: 1|cmake -DCMAKE_TOOLCHAIN_FILE=myToolchain.cmake .. |// and created a toolchain file in|project/myToolchain.cmake|. Using relative path CMake first looks relative to the top of the build directory, then if not found there, relative to the top of the source di

Re: [CMake] question about version details in source code

Am 17.07.19 um 15:38 schrieb hex: hello community, I am receiving a|fatal error: foobar_version.h: No such file or directory|for|foobar_version.h|. The reason is that the source file is generated in|${CMAKE_CURRENT_BINARY_DIR}/foobar_version.cpp|while the header file is in|${CMAKE_CURRENT_SO

Re: [CMake] cmake - two targets that depends on single static library that should be compiled based on the target that is being built

> > > I have a static library and two target executables, let's call them > **libA**, **EXE1**, **EXE2**. > > If I am building EXE2, I need to disabled the macros in libA and don't > link to another library. > [...] > I don't want to create two targets with same source files. > I'm curious why you

[CMake] question about version details in source code

hello community, I am receiving a|fatal error: foobar_version.h: No such file or directory|for|foobar_version.h|. The reason is that the source file is generated in|${CMAKE_CURRENT_BINARY_DIR}/foobar_version.cpp|while the header file is in|${CMAKE_CURRENT_SOURCE_DIR}|as seen here: 1234|confi