[CMake] Enabling Fortran only builds with Cmake 3.10.2 on Windows

2018-03-23 Thread Belcourt, Kenneth
Hi, I have a project that builds fine on Mac and Linux by disabling C/C++ and building with only Fortran. PROJECT(Noel LANGUAGES Fortran) When I try to build on Windows, it seems that CMake is looking for variable VCTargetsPath, here’s the error: Setting environment for using Microsoft Visu

Re: [CMake] build times increase 1.5x from cmake 2.8.12 to 3

2018-03-23 Thread Robert Maynard
My initial thought is that the differences between -mmd and -md would be pretty minimal. The original discussion on this change ( https://cmake.org/Bug/view.php?id=14914 ) has people agreeing with that as this information is generated when the compiler builds each file. Have you used something lik

[CMake] build times increase 1.5x from cmake 2.8.12 to 3

2018-03-23 Thread Miller Henry
I have a fairly large project that I'm trying to update from building with cmake 2.8.12 to 3.10.2. When I make the change my build times go up by half on our Jenkins ci build system. The build machines are 32 core and my build time goes from 59m 38s to 1h 28m 33s. When I try this locally the ti

[CMake] adding cmake managed external projects with their config

2018-03-23 Thread Stéphane Ancelot
Hi, I have an experimental Bullet package I would like to use, but I don't manage to override the system CMAKE_MODULE_PATH for bullet to use the new one. I tried using ExternalProject_Add (Bullet   SOURCE_DIR "bullet3/build_cmake") but this does not seem the RIGHT way... Overriding CM

Re: [CMake] should zlib be searched in CMAKE_PREFIX_PATH or am I confused?

2018-03-23 Thread Eric Noulard
2018-03-23 11:44 GMT+01:00 Mario Emmenlauer : > > Hi Eric, > > On 23.03.2018 10:58, Eric Noulard wrote: > > 2018-03-23 10:21 GMT+01:00 Mario Emmenlauer >: > > > > > > Thanks PF, I think this makes more sense now! I was assuming that > > cmake always prefers CMA

Re: [CMake] should zlib be searched in CMAKE_PREFIX_PATH or am I confused?

2018-03-23 Thread Mario Emmenlauer
Hi Eric, On 23.03.2018 10:58, Eric Noulard wrote: > 2018-03-23 10:21 GMT+01:00 Mario Emmenlauer >: > > > Thanks PF, I think this makes more sense now! I was assuming that > cmake always prefers CMAKE_PREFIX_PATH over builtin paths. But as you > clarified

Re: [CMake] should zlib be searched in CMAKE_PREFIX_PATH or am I confused?

2018-03-23 Thread Eric Noulard
2018-03-23 10:21 GMT+01:00 Mario Emmenlauer : > > Thanks PF, I think this makes more sense now! I was assuming that > cmake always prefers CMAKE_PREFIX_PATH over builtin paths. But as you > clarified, that only applies to libraries that provide find_package > support. > > This is actually quite un

[CMake] Suppressing LINK_WHAT_YOU_USE warning

2018-03-23 Thread Nikos Chantziaras
When using the LINK_WHAT_YOU_USE feature to detect unneeded library dependencies in a C++ project, I get this: Unused direct dependencies: /lib64/libm.so.6 It seems CMake should be smart enough to suppress this, as it doesn't seem possible to not link against libm? Is there a way to

Re: [CMake] find_package() for static only / shared only

2018-03-23 Thread Mario Emmenlauer
Two thumbs up for this! :-) On 23.03.2018 03:14, Ray Donnelly wrote: > Our why doesn't cmake set a long needed standard here of .dll.lib and be done > with this nonsense? > > On Thu, Mar 22, 2018, 11:58 PM P F via CMake > wrote: > > Why not install shared librarie

Re: [CMake] find_package() for static only / shared only

2018-03-23 Thread Mario Emmenlauer
Dear PF, thanks! I think this is a quite sensible approach and I will do as you suggest. I did not consider it at first because there are some packages that can install static and shared side-by-side. But I agree that your suggestion is ore pragmatic and also less error-prone. All the best,

Re: [CMake] should zlib be searched in CMAKE_PREFIX_PATH or am I confused?

2018-03-23 Thread Mario Emmenlauer
Thanks PF, I think this makes more sense now! I was assuming that cmake always prefers CMAKE_PREFIX_PATH over builtin paths. But as you clarified, that only applies to libraries that provide find_package support. This is actually quite unfortunate. Then I don't see an easy way to enforce usage of