[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-405-g07226324eb

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 76ef7d3988..3f65c674a4 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 16) -set(CMake_VERSION_PATCH 2019

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-404-g52accc779e

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc4-4-g602f2118b0

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-400-gad815939c9

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-388-gd9cf0ec4d4

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc4-2-g2a2c890023

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

Re: [CMake] Missing dll on program startup - a way automate it?

Can also add install rules so you get an INSTALL target, and then you can just build that, and everything will end up in the right place. On Thu, Nov 21, 2019 at 3:56 AM Fred Baksik wrote: > Adding the relevant directories to PATH in the debugger or build > environment should allow them to be

Re: [CMake] Missing dll on program startup - a way automate it?

Adding the relevant directories to PATH in the debugger or build environment should allow them to be found. On Wed, Nov 20, 2019, at 3:32 AM, Petr Kmoch wrote: > Hi. > > I haven't used it yet, but I believe the target property >