[Cmake-commits] CMake branch, next, updated. v3.4.0-1603-g064ad91

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

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On 12/02/2015 10:31 AM, Levi Morrison wrote: > Hmm. What is the purpose of this module? I verified that indeed my > changeset somehow breaks this test but I don't even understand what it > is trying to do. At a glance it looks like even *more* duplication of > feature detection. Please tell me I'm

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On Tue, Dec 1, 2015 at 11:11 AM, Brad King wrote: > On 12/01/2015 12:47 PM, Levi Morrison wrote: >> I am having trouble reproducing this failure. When I do an >> unrestricted ctest (test everything) it will fail, but if I do >> something like `ctest -VV -R

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

> On 12/01/2015 05:11 PM, Roger Leigh wrote: >> Attached. I also attached the BoostScanDeps raw output and after >> search-and-replace to make into valid cmake conditionals, and then after >> simplifying where following release dependencies are unchanged, so you >> can see where the logic in

[Cmake-commits] CMake branch, next, updated. v3.4.0-1601-ge5ecb12

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-656-g6f6897f

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

[Cmake-commits] CMake branch, release, updated. v3.4.0-43-gfd7180f

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 fd7180f0c0c2554c31afda235469df986a109fe4 (commit) from

[cmake-developers] [PATCH] FindTIFF: Add imported targets

- Add TIFF::TIFF imported target - Document imported target - Add testcase to test the standard variables and the imported target Also: - Add TIFF_INCLUDE_DIRS to match common practice - Update documentation generally, including documenting TIFF_INCLUDE_DIRS Patch attached. Regards,

[Cmake-commits] CMake branch, next, updated. v3.4.0-1607-g1c27e7d

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1605-gb2ae6a3

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

[cmake-developers] [PATCH] FindTIFF: Add imported targets

- Add TIFF::TIFF imported target - Document imported target - Add testcase to test the standard variables and the imported target Also: - Add TIFF_INCLUDE_DIRS to match common practice - Update documentation generally, including documenting TIFF_INCLUDE_DIRS Patch actually attached this

Re: [CMake] How to generate for Ninja + MSVC?

On Wed, Dec 2, 2015 at 1:29 PM, Nils Gladitz wrote: > On 02.12.2015 20:18, Robert Dailey wrote: >> >> Is there a way to generate for Ninja using MSVC toolchain? If so, how >> do I do that? Do I need a toolchain file? > > > You can select the Ninja generator (e.g. cmake -G

Re: [CMake] How to generate for Ninja + MSVC?

On 02.12.2015 20:18, Robert Dailey wrote: Is there a way to generate for Ninja using MSVC toolchain? If so, how do I do that? Do I need a toolchain file? You can select the Ninja generator (e.g. cmake -G Ninja) while running cmake from the desired Visual Studio command line environment.

[Cmake-commits] CMake annotated tag, v3.4.1, created. v3.4.1

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 annotated tag, v3.4.1 has been created at 1c011d39bb252d7f314eb837061d8dddc9bd1ce3 (tag) tagging

[CMake] How to generate for Ninja + MSVC?

Is there a way to generate for Ninja using MSVC toolchain? If so, how do I do that? Do I need a toolchain file? -- 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 support the CMake

[Cmake-commits] CMake branch, maint, updated. v3.4.1

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, maint has been updated via fd7180f0c0c2554c31afda235469df986a109fe4 (commit) via

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

02.12.2015, 22:55, "Robert Maynard" : > We are pleased to announce that CMake 3.4.1 is now available for download. > > Please use the latest release from our download page: >   https://cmake.org/download/ > > Thanks for your support! Good job! Thank you! I could not

Re: [CMake] How to generate for Ninja + MSVC?

On Wed, Dec 2, 2015 at 1:37 PM, Robert Dailey wrote: > On Wed, Dec 2, 2015 at 1:29 PM, Nils Gladitz wrote: >> On 02.12.2015 20:18, Robert Dailey wrote: >>> >>> Is there a way to generate for Ninja using MSVC toolchain? If so, how >>> do I do that?

[cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

We are pleased to announce that CMake 3.4.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.4.1 since 3.4.0: Bill

[cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

We are pleased to announce that CMake 3.4.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.4.1 since 3.4.0: Bill

[CMake] [ANNOUNCE] CMake 3.4.1 available for download

We are pleased to announce that CMake 3.4.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.4.1 since 3.4.0: Bill

Re: [CMake] How to generate for Ninja + MSVC?

On 12/2/2015 2:39 PM, Robert Dailey wrote: For some reason Strawberry Perl installed gcc/g++ to my PATH. I removed this and it's finding MSVC 19 now. Thanks. Could also set CC and CXX to cl before running CMake. -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065

[cmake-developers] [CMake 0015870]: "cmake -E copy" command do not display error if source is directory

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15870 == Reported By:gang65 Assigned To:

Re: [CMake] Best way to handle application data path for local run vs. installation

On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote: > On 02-Dec-15 05:13, Alexander Neundorf wrote: ... > > well, the RPATH entry was not designed to be patched, > > RPATH designed to be patched. And since it's a third time I'm making > this statement please provide any arguments if

Re: [CMake] generator expression for set_target_properties

Hi Lloyd, You mean like: if( ${CMAKE_BUILD_TYPE} STREQUAL "Release" ) set_target_properties( myexec PROPERTIES WIN32_EXECUTABLE TRUE ) endif() ? Or would you like the build configuration to change in this respect when you change the build type in the IDE? This latter may not be possible to

Re: [CMake] How to generate for Ninja + MSVC?

On 12/2/2015 8:22 PM, iosif neitzke wrote: Isn't this what Generator Toolset selection is for? ex. cmake -G Ninja -T v140 http://cmake.blogspot.com/2013/05/cmake-2811-available-for-download.html No, that is for telling the VS IDE which tool set to use. It has no effect on the Ninja

Re: [cmake-developers] Fw: Please comment on ios-universal topic

On 02-Dec-15 19:44, Bartosz Kosiorek wrote: Hi. Currently we already support similar target properties: - INSTALL_NAME_DIR - INSTALL_RPATH - INSTALL_RPATH_USE_LINK_PATH It will be great to follow the same name convention. Because this new property is only applicable for INSTALL step, I would

Re: [CMake] How to generate for Ninja + MSVC?

Alternate solution is to define following environment variables: * CC=cl.exe * CXX=cl.exe In this case, CMake will search these compilers rather than the standard choices (starting with c++ and g++ for C++ language). And you don’t have any longer constraints about your environment. Marc

Re: [cmake-developers] Fw: Please comment on ios-universal topic

Thanks Ruslan for feedback. I think that this new property should work also for FRAMEWORK and should support both OSX and iOS In that way it is already done for: - for SHARED library adding FRAMEWORK property produce correct Framework for iOS or OSX (for Cmake 3.5 the documentation was

Re: [CMake] How to generate for Ninja + MSVC?

Ah, okay, thanks. From cmake-gui the solution equivalent would be selecting the Ninja generator but specifying native compilers (cl.exe for this example) instead of using the default native compilers? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[Cmake-commits] CMake branch, master, updated. v3.4.1-614-g4ffeab0

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

[CMake] generator expression for set_target_properties

Hi, We have a cmake file for Qt project. We want to hide the console from release build. For that we are using ADD_EXECUTABLE(myexec ${MYEXEC_SRC} ) SET_TARGET_PROPERTIES(myexec PROPERTIES WIN32_EXECUTABLE true) Is it possible for me to set this property only for the release build? I am using

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.1 available for download

Meet the fresh update online installers (CMake3.4.20151203): http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe and http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe If you have used them previously, then just update via "CMake Maintenance Tool". 02.12.2015, 23:55,

[cmake-developers] [PATCH] Extend copy and copy_if_different commands with support multiple files

Hi. This patch allows to use multiple files in commands "copy" and "copy_if_different". Input files could be merged with wildcards. For example: ./bin/cmake -E copy bin/* CMakeFiles/* file.tar dupajasia If wrong file path were provided as input then the error will be displayed, but rest

[cmake-developers] Fw: Please comment on ios-universal topic

Hi. Currently we already support similar target properties: - INSTALL_NAME_DIR - INSTALL_RPATH - INSTALL_RPATH_USE_LINK_PATH It will be great to follow the same name convention. Because this new property is only applicable for INSTALL step, I would like to propose to rename property name to

[Cmake-commits] CMake branch, next, updated. v3.4.0-1572-ge76cbcc

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1574-g4f5acd5

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-637-gd956816

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-632-g36e6ee9

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-635-g5257a3b

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1581-g723ae59

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1583-g7fe51ef

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-641-gda78a16

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1586-gf0acaa7

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1594-g5fe8cb9

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

[CMake] CPack-NSIS Start menu item not created

Hi, Hi I am using CMake for building and packing on Windows. I have a root cmake file and the subfolders contains executable and other modules. I am writing the packing code in the root cmake file and executable contained in a subfolder. My executable name is myexec, and I want to create start

[Cmake-commits] CMake branch, master, updated. v3.4.0-629-g88c2d4b

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-650-g3fa2fc7

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-654-g4e29a51

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1591-g8114424

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

[cmake-developers] [PATCH] Fix Resource directory structure for iOS Bundles (Framework and Application), update Tests and Help

Hello. Patch in attachment allows to place resources in main Bundle directory (iOS specification), instead to always place in Resource directory (OSX specification. See more: https://public.kitware.com/Bug/view.php?id=15848 ? I tested it intensively with different generators (Makefile,

Re: [CMake] Best way to handle application data path for local run vs. installation

On 30/11/2015 02:10, Dmitry Marakasov wrote: Hi! This question bugs me for a long time so I though maybe someone has a solution. I have a project which includes an application and some data for it. An application needs to know path to its data files, so I pass it via compiler definition:

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 12/01/2015 05:11 PM, Roger Leigh wrote: > Attached. I also attached the BoostScanDeps raw output and after > search-and-replace to make into valid cmake conditionals, and then after > simplifying where following release dependencies are unchanged, so you > can see where the logic in

Re: [CMake] How to generate for Ninja + MSVC?

Isn't this what Generator Toolset selection is for? ex. cmake -G Ninja -T v140 http://cmake.blogspot.com/2013/05/cmake-2811-available-for-download.html -- 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

Re: [CMake] Best way to handle application data path for local run vs. installation

On 03-Dec-15 04:34, Alexander Neundorf wrote: On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote: > On 02-Dec-15 05:13, Alexander Neundorf wrote: ... > > well, the RPATH entry was not designed to be patched, > > RPATH designed to be patched. And since it's a third time I'm