[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-203-g4d9d674

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 9086fb2..9eb3ade 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180712) +set(CMake_VER

Re: [CMake] Development Workflow with CMake and VS2017

Hello! I usually just download prebuild binaries if they are available or build the required dependency from sources. There are some libraries (and other software) that are not Windows-friendly (These products are still considered cross-platform and usually are free in the way fanatics from FSF

[CMake] Development Workflow with CMake and VS2017

Hello list, I apologize if this is slightly offtopic, but I have not yet found a good way to manage dependencies on Windows. On Linux the dependencies can be installed system wide, but on Windows this is typically not the case. I did see some CMake scripts that would download and install things

[Cmake-commits] CMake branch, release, updated. v3.12.0-rc3-4-g730c8b8

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 730c8b87275ca9a95f90cea745532f49d6fdd05d (commit) via

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-202-gbfb025f

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 bfb025f04b3522ff0fee650e7c4c4fe808d739b3 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-200-gf7f2b80

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 f7f2b8078e6181f0f3c476c55d7cab3d86ffdaae (commit) via

Re: [CMake] Concurrency issues with copy_if_different

Had the same problem and went with #2 -Caleb On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette wrote: > Hello, > > in one of our projects, we use copy_if_different to copy some DLLs > required by the runtime. It's called as post-build action. The problem > is that several targets want to copy

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-190-g7b04ad6

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 7b04ad61cf925161c8b7f9abf6ef3db047118807 (commit) via

[CMake] FindMPI and version

It appears that MPI__VERSION is returning the version of the MPI _standard_ that is supported by the chosen MPI. While I am sure this is useful in some contexts, it’s actually not what I want/need for my project and it is quite inconsistent with analogous versions such as

Re: [CMake] Concurrency issues with copy_if_different

Personally would go with option number 2 On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette wrote: > Hello, > > in one of our projects, we use copy_if_different to copy some DLLs > required by the runtime. It's called as post-build action. The problem > is that several targets want to copy the

Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?

Hello! First of all, I suggest you use Boost imported targets instead of Boost_INCLUDE_DIRS and Boost_LIBRARY_DIRS and the target_include_directories() and target_link_libraries() functions. Al this is to better support exporting CMake package if you need it. If you do not produce CMake package

[CMake] Boost + CMake + Windows + Sanity -> Possible?

Hello! First the short version... Can anyone give me a set of instructions to download, build and setup the latest Boost (currently 1.67) on Windows 10 for VS 2017 64bit such that the following will work... find_package(Boost REQUIRED COMPONENTS system filesystem thread date_time