[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-224-gac5b80e

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

Re: [CMake] Single Letter Omissions From File Path In Linker

On 10/14/2016 08:04 AM, Randy Turner wrote: > As you can see, the file path is missing a "t" in the first occurrence > of the word "iterator" and so that file definitely does not exist. A > file exists in the location with correct spelling, but somehow that > hardcoded path in that temporary file

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-492-g2af5a40

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-490-gc7a826a

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

Re: [CMake] Force copy of files

"copy" should always overwrite. "copy_if_different" will conditionally overwrite, only if the contents of the two files are different. If "copy" was not overwriting something when it should have been, please send steps to reproduce the issue, because that would be a bug. HTH, David C. On

Re: [CMake] Force copy of files

Never mind, figured this one out: use copy_if_different On Fri, Oct 14, 2016 at 1:34 PM, Aaron Boxer wrote: > I have the following lines in my cmake file > > > foreach(f ${MyFiles}) > add_custom_command(TARGET ${OPENJPEG_PLUGIN_NAME} PRE_BUILD >

[CMake] Force copy of files

I have the following lines in my cmake file foreach(f ${MyFiles}) add_custom_command(TARGET ${OPENJPEG_PLUGIN_NAME} PRE_BUILD COMMAND ${CMAKE_COMMAND} -E copy ${f} $) endforeach() in order to copy MyFiles to MyFolder.

Re: [CMake] Single Letter Omissions From File Path In Linker

On 10/14/2016 10:04 AM, Randy Turner wrote: Hello! I've been running into a frustrating issue on and off for the past year. The project will build the source files correctly but when it comes to linking the executables, I always get the same error. The specific file varies, but the failure mode

[Cmake-commits] CMake branch, release, updated. v3.7.0-rc1-46-ga975b21

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-488-ge0a44b6

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-223-g0d81863

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

Re: [CMake] Single Letter Omissions From File Path In Linker

On Fri, Oct 14, 2016 at 9:04 AM, Randy Turner wrote: > Hello! I've been running into a frustrating issue on and off for the past > year. The project will build the source files correctly but when it comes > to linking the executables, I always get the same error. The

[CMake] Single Letter Omissions From File Path In Linker

Hello! I've been running into a frustrating issue on and off for the past year. The project will build the source files correctly but when it comes to linking the executables, I always get the same error. The specific file varies, but the failure mode is always the same. For example:

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-482-gee304e8

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-478-g1ed28ad

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-218-ga8513d8

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-474-gfd1f119

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-476-ged05c2d

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-472-g2b1e512

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-208-g8b49667

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-206-gdabd177

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-202-gf0579e2

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-204-g03622ee

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-215-geb923da

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-213-g02946e0

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-464-g14ab1e9

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-462-g7509065

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

Re: [CMake] make_directory deprecated. What's the correct solution to generate directories at build time now?

You are right! The documentation quick search for the "make_directory" keyword does not find the cmake executable documentation (i.e. the make_directory command-line tool), only the script command. That tripped me up. If you manually go to the cmake executable documentation (

Re: [CMake] How to handle options with more than two possible values?

Thanks it works perfectly! On Thu, 13 Oct 2016 13:41:00 +0200 Petr Kmoch wrote: > Hi. > > option() is a handy shortcut for boolean options, but it's little more than > syntactic sugar for a cache variable of type BOOL. To create a tristate > variable, you can do this: >