[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-198-g4c921e5

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

Re: [CMake] Need help generating a config file

Eric, thanks, I figured it out. On Thu, Oct 13, 2016 at 3:27 PM, Eric Noulard wrote: > > > 2016-10-13 21:18 GMT+02:00 Aaron Boxer : > >> Hello, >> >> I have a foo.h.cmake.in file that I am using to generate a >> foo_config.hfile. >> >> Here

Re: [CMake] Need help generating a config file

Thanks a lot, Eric. So, I have two cmake variables, and I want to #define FOO_DEFINE if one or the other is set, otherwise I don't want FOO_DEFINE defines at all. Is this possible ? On Thu, Oct 13, 2016 at 3:27 PM, Eric Noulard wrote: > > > 2016-10-13 21:18 GMT+02:00

Re: [CMake] Need help generating a config file

2016-10-13 21:18 GMT+02:00 Aaron Boxer : > Hello, > > I have a foo.h.cmake.in file that I am using to generate a > foo_config.hfile. > > Here is the line in my cmake file that generates the header: > > configure_file(${CMAKE_CURRENT_SOURCE_DIR}/foo.h.cmake.in >

[CMake] Need help generating a config file

Hello, I have a foo.h.cmake.in file that I am using to generate a foo_config.hfile. Here is the line in my cmake file that generates the header: configure_file(${CMAKE_CURRENT_SOURCE_DIR}/foo.h.cmake.in ${CMAKE_CURRENT_BINARY_DIR}/foo_config.h @ONLY) I would like to define or

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-460-g0be1721

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-458-g70184a7

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-454-g4edd6e2

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

[CMake] PROPERTIES VERSION bug in windows DLL major.minor version

Hi, I noticed that on an older (3.2.2) release I was using with Win7, the behaviour described about automatically parsing VERSION major.minor and putting it into the DLL image version wasn't behaving correctly. It seemed it was applying the VERSION from the first shared library in my project, to

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-452-gec4d7d2

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-447-gb0ab354

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-444-g49fe82b

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-rc1-38-gd0255d5

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-197-gac5c492

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-439-gc942de4

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-191-g9273eed

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-193-gd61bfcb

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-436-g1ae7aa2

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-433-gc481462

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-431-g605a85b

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-429-g48e27d6

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-427-g0fb7df0

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-176-g2be36b0

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-189-g1b592b6

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-180-g30fe9f0

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-171-g3b07c58

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-178-gbd74517

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-173-g9d0e556

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-169-g0123500

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-418-gba0bb60

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

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

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: set(ENABLE_SOMETHING AUTO CACHE STRING "Enable SOMETHING support") # create the variable set_property(CACHE

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

Hello, Regarding the cmake-commands manual [1], the "option" command seems to take as argument a boolean constant that can have the two possible values: ON or OFF. I would like to use three possible values for an option: AUTO (as default value), ON or OFF. Example: option(ENABLE_SOMETHING

[cmake-developers] [patch] Add support for Ice 3.6.3 to FindIce

Branch: ice-3.6.3. Pushed to next for testing. This is for a new point release recently issued by upstream. Regards, Roger -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-416-g5ee591d

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