[Cmake-commits] CMake branch, master, updated. v3.7.1-869-g6100155

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

Re: [CMake] Best Practise for Multiple Platforms of External Project

You could try using file(MAKE_DIRECTORY ...) between the two ExternalProject_Add() calls to actually ensure the directory exists, but I'm not 100% sure whether this would not interfere with the download step when it goes to do that at build time. I'm pretty sure it works, but you should confirm

[Cmake-commits] CMake branch, next, updated. v3.7.1-1744-g08aac83

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, next has been updated via 08aac8319d907b36b1ae65803adf5079109168e6 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1742-g211f798

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, next has been updated via 211f798e466bc225dccd2aad89c3c24d02b66bdc (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1740-g402bb3c

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, next has been updated via 402bb3c1f1762f03d29e735a129ab9f6419e4d66 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1738-g0c61ea6

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, next has been updated via 0c61ea6263aac5c8d98eb72a1478c2032b65b014 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1736-g21eecae

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, next has been updated via 21eecae3d33670082ba19e6380adee9bfff0ba18 (commit) via

[CMake] checking for cmake predefined targets

Hi list. With Visual Studio generator, is there a way, at configuration time, to check for the existence of INSTALL, PACKAGE and RUN_TESTS targets? Seems they only present when the configuration files have an install(), enable_testing() or include(CPack) commands somewhere. I need this

[Cmake-commits] CMake branch, next, updated. v3.7.1-1734-g4bf498e

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, next has been updated via 4bf498e9618c6d70e642a5a58c49f222f8f2b575 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1731-g820267f

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, next has been updated via 820267ff71a81546c420e1257bbdc4d72dad8a46 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.1-866-gc241679

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-868-g10ca398

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

[CMake] Best Practise for Multiple Platforms of External Project

Hi In my project I have to compile the same external projects by the different generators, is that possible to handle this cases by ExternalProject_Add ? I tried this way, firstly, just download the repository ExternalProject_Add(OPENEXR_DOWNLOAD PREFIX ${OPENEXR_PREFIX} GIT_REPOSITORY