, Lectem.
11:43, 13 January 2019 г., Lectem :
Hi,
Is there a way to list all the packages (both config files and find-modules)
that find_package could find ?
Could we even imagine this would also permit to list the variables and targets
created in it ?
I think that would be a very helpful to
when you don’t have access to the system having issues (user bug
reports for example).
Cheers,
Lectem
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
r than
converting everything to a new format.
Wouldn’t that create more confusion ? I fear it’d end up as a python2 python3
issue, where both versions look alike but are incompatible.
Have a nice Week-end,
Lectem
--
Powered by www.kitware.com
Please keep messages on-topic and check the C
Because you are looking at an old CMake version 😉
I think it was introduced in cmake 3.8.2 ?
De : Florian Lindner
Envoyé le :dimanche 5 novembre 2017 17:03
À : cmake@cmake.org
Objet :Re: [CMake] target_compile_features question
Am 05.11.2017 um 15:07 schrieb Jan Christoph Uhde:
> Hi,
>
> I hav
Right, as mentionned by Craig Scott, a script might do the trick ? Just a
cmake-gui.bat that calls cmake-gui.exe should work.
De : Robert Maynard
Envoyé le :lundi 14 août 2017 15:24
À : Craig Scott
Cc : Clément Gregoire; CMake
Objet :Re: [CMake] cmake-gui on windows and qt5 dlls
More importantly
OK so I ended up doing the following :
Use a cmake script to detect coverage support and set up a new build type
+
Let CTest run GCov for me
Final result can be seen here : https://github.com/Lectem/cpp-boilerplate
link to the Coverage setup script :
https://github.com/Lectem/cpp-boilerplate
I think that you are looking for the toolchain files :
https://cmake.org/cmake/help/v3.0/manual/cmake-toolchains.7.html
The other option is to use a cmake script to specify your variables which
includes CMakelists.txt (or the other way around if you can modify the
CMakelists.txt). This would be
a Windows/MSYS related problem (I think it is), but I
really don’t understand why CMAKE wants to use C:/msys64/mingw64/bin/ar.exe so
much and not the one in CMAKE_AR / CMAKE_CXX_COMPILER_AR…
If you guys have any idea.
Thanks,
Lectem
--
Powered by www.kitware.com
Please keep messages on-topic
I managed to get it working by using an intermediate script.
One might want to generate the script instead of using the « RUN_IT » variable
trick.
This was only tested on Windows, but seems to work fine.
Put the following code in a xx.cmake file, include it from your
CMakeLists.txt and enjoy.