[CMake] Ninja generator and showIncludes

Hello. I have been searching for a way to prevent the Ninja generator from issuing the showIncludes command to cl. With our update to the latest CMake (3.8.2) on Windows (7 enterprise, at work) with the latest MSVC (2017 community), we now have a ton of messages saying Note: including file:

[CMake] GetPrerequisites with Android?

Has anyone used GetPrerequisites[1] when cross-compiling a shared library with Android NDK toolchain? I'd like some way to get dependent *.so files (located in the NDK itself and specified on the linker command line when building) so I can copy them to my android java project dir under "libs" so

[CMake] fortran linking issue

When I set the linker language of a fortran program to "C", it automatically links in -lgfortran, -lquadmath, -lm. SET_TARGET_PROPERTIES(main_f PROPERTIES LINKER_LANGUAGE "C") Unfortunately, that precludes me linking in static versions of -lquadmath. How do I tell CMAKE not to append these

Re: [CMake] fortran linking issue

It turns out these linker flags were being added by cmake. To disable them, I had to: unset(CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES) I was then able to use SET_TARGET_PROPERTIES to link into the static versions of the code I wanted. This also fixed the issue for the case where I had a C++ exe

[CMake] How to add project files?

Hello, our project, which is currently using scons is structured like this ROOT - SConstruct - CMakeLists.txt - src/ - SConscript - CMAkeLists.txt - Module1 - somesourcefiles.cpp - tests/ - testsourcefiles.cpp - config/ - configsourcefile.cpp

Re: [CMake] /path/to/libpng.so automatic conversion to -lpng ?

2017-07-13 2:04 GMT+02:00 René J. V. Bertin : > Andreas Naumann wrote: > > > cmake instrospects your compiler and asks for system directories. > > Just stumbled across this documentation tidbit: > Thanks you for digging this. I totally ignored that "feature". > > >>>

Re: [CMake] /path/to/libpng.so automatic conversion to -lpng ?

2017-07-13 12:07 GMT+02:00 René J. V. Bertin : [...] > > > > > The thing I don't understand is that you use CMake 3.8.2 so you should > get > > the new behavior. > > Are you sure? I read from the description above that you have to set the > policy > explicitly. > You are

Re: [CMake] /path/to/libpng.so automatic conversion to -lpng ?

Eric Noulard wrote: > Thanks you for digging this. > I totally ignored that "feature". I guess most of us did, it's one of those things that usually works just fine but that when it breaks sends you on a nasty quest to figure out WTF is going on (IOW, makes you doubt yourself until you

Re: [CMake] /path/to/libpng.so automatic conversion to -lpng ?

Eric Noulard wrote: > From the command line I doubt it. Adding -DCMAKE_POLICY_DEFAULT_CMP0060=NEW on the commandline works. But whatever the reason, using PNG::PNG works too. Apparently policy 60 doesn't affect the IMPORTED_LOCATION target property... > Did you try to use ninja generator

Re: [CMake] /path/to/libpng.so automatic conversion to -lpng ?

2017-07-13 13:01 GMT+02:00 René J. V. Bertin : > Eric Noulard wrote: > > > From the command line I doubt it. > > Adding -DCMAKE_POLICY_DEFAULT_CMP0060=NEW on the commandline works. > Good to know. > > But whatever the reason, using PNG::PNG works too. Apparently policy 60

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc6-284-g4b460a5

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 4b460a5ba8cdb36e05c1517237c8ef15562e4490 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc6-2-gd11c48e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via d11c48e0e344e6758a5575330b3f0e267d820e02 (commit) via

Re: [cmake-developers] Using USES_TERMINAL in ExternalProject.cmake

On 13.07.2017 22:19, Robert Dailey wrote: I noticed that ExternalProject_Add() has this same issue when run from Ninja. I do not see real-time output of the progress. Would it work to set USES_TERMINAL for most (if not all) custom commands and targets in ExternalProject.cmake? See the

[cmake-developers] Using USES_TERMINAL in ExternalProject.cmake

In my own personal usage of add_custom_target() and add_custom_command(), I use USES_TERMINAL so that stdout and stderr from commands that are actively running get output in more real-time. I've only tested this using the Ninja generator, and seems to improve output behavior. Without it, I notice

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc6-285-g52db8d5

_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170713) +set(CMake_VERSION_PATCH 20170714) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc6-263-ge5c762d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e5c762d32d8a1329aac66a66eaf634a009cb288b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc6-280-gaa97170

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via aa97170f2b25a99d2cc69fd6b2a059e52872f341 (commit) via