[Cmake-commits] CMake branch, master, updated. v3.8.0-1007-g7382523

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

[cmake-developers] Issues with overriding Python version, possible bug?

My use case (which I am pretty sure is a common one) is that for PLplot I want the default behaviour of our build system to be that it looks for Python 3, but if that does not exist it looks for Python 2. It appears the following logic implements that desired default behaviour.

Re: [CMake] DLL handling under CMake

Am 27. April 2017 10:43:50 MESZ schrieb Louis-Paul CORDIER : >This steps are tedious and I'm wondering if there is a mechanism that >exists or that have to be imagined to make the DLL nightmare end. I use BundleUtilities to achieve the copying of DLL files to the

Re: [CMake] DLL handling under CMake

Our project uses some custom cmake functions to gather the DLLs from 3rd party libs (HDF5, TBB, Qt) and create custom targets to copy them to the build directory and create install rules to copy them to the package when it is created. Yes, they were tedious to write and get correct but they