Re: [CMake] Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing 2017... sigh.

2018-10-01 Thread J. Caleb Wherry
The Visual C++ team sheds a little more light on this: https://blogs.msdn.microsoft.com/vcblog/2018/10/01/cuda-10-is-now-available-with-support-for-the-latest-visual-studio-2017-versions/ Glad they listened to the community and worked with NVIDIA to make this work. We’ve been holding off migrati

[CMake] Writing foo-config.cmake with find_dependency

2018-10-01 Thread Mateusz Loskot
Hi, After 10+ years of maintaining a horrible kind o CMake configuration for a project I maintain, SOCI [1], I'm in the middle of rewriting it [2] according to the modern CMake principles. At least, I'm trying to. The library has number of dependencies on third-party libraries, namely database ac

Re: [CMake] Computation of CMAKE_OSX_SYSROOT

2018-10-01 Thread Robert Maynard
Documentation changes can be done through the CMake project hosted on gitlab. You would want to modify the file: https://gitlab.kitware.com/cmake/cmake/blob/master/Help/variable/CMAKE_OSX_DEPLOYMENT_TARGET.rst On Mon, Oct 1, 2018 at 11:13 AM James Turner via CMake wrote: > > > On 1 Oct 2018, a

[CMake] Boost CMake support

2018-10-01 Thread Robert Ramey
Boost Library developers are taking a serious look at making Boost more friendly for users of CMake. This discussion is taking place on the Boost Developer's mailing list. https://www.boost.org/community/groups.html Those who have an interest in this topic are encouraged to observe and/or pa

Re: [CMake] protobuf and imports relative to root (and --proto_path)

2018-10-01 Thread David Jobet
Tx Alexander. Unfortunately, the version of cmake that we use (2.6.0) does not have a --dependency_out arg. So I just coded a small python parser that recursively check for imports and create a ninja depfile out of it. (injected with DEPFILE in custom command) It looks like it works fine thanks

Re: [CMake] Computation of CMAKE_OSX_SYSROOT

2018-10-01 Thread James Turner via CMake
> On 1 Oct 2018, at 14:25, Craig Scott wrote: > > You need to set CMAKE_OSX_DEPLOYMENT_TARGET as a cache variable before > calling the project() command. If you set it as a normal (i.e. non-cache) > variable, the compiler detection logic triggered by the project() call > creates a cache vari

[CMake] iOS CMAKE_INSTALL_COMBINED breaks RPath settings

2018-10-01 Thread Curtis Mahieu
I'm using CMake 3.12.2 and having an issue with cmake messing up the RPaths for the final outputted shard Frameworks after doing a cmake --build . --target install The output of my build is three shared Frameworks A, B and C A is the common library that B and C link against. A /\ B

Re: [CMake] Computation of CMAKE_OSX_SYSROOT

2018-10-01 Thread Craig Scott
On Mon, Oct 1, 2018 at 10:53 PM James Turner via CMake wrote: > Hi, > > The docs here: > > https://cmake.org/cmake/help/v3.12/variable/CMAKE_OSX_SYSROOT.html > > state that CMAKE_OSX_SYSROOT is computed from CMAKE_OSX_DEPLOYMENT_TARGET > if not explicitly set. Can anyone comment on how th

[CMake] Computation of CMAKE_OSX_SYSROOT

2018-10-01 Thread James Turner via CMake
Hi, The docs here: https://cmake.org/cmake/help/v3.12/variable/CMAKE_OSX_SYSROOT.html state that CMAKE_OSX_SYSROOT is computed from CMAKE_OSX_DEPLOYMENT_TARGET if not explicitly set. Can anyone comment on how this works, because in my setup it seems to be failing. This showed up as -is