[cmake-developers] [CMAKE][PATCH] fix create_javah on Windows

Hi, Attached is a patch fixing erroneous handling of CLASSPATH parameter for function create_javah (module UseJava). Update tests accordingly. Marc 0001-Fix-create_javah-CLASSPATH-handling-on-Windows.patch Description: 0001-Fix-create_javah-CLASSPATH-handling-on-Windows.patch -- Powered

Re: [CMake] cdash/ctest question

Alex Thank you for this information. I shall test this out right away. Yours JB -Original Message- From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net] Sent: 14 January 2016 23:17 To: cmake@cmake.org Cc: Biddiscombe, John A. Subject: Re: [CMake] cdash/ctest question On Thursday,

[CMake] add_custom_command scope

Hello, Using CMake 3.3 and VS2012. The below cmake scripts generate "Policy CMP0040 is not set: The target in the TARGET signature of add_custom_command must exists". Why cannot the custom/CMakeLists.txt file see the target created in app/CMakeLists.txt ? Moving the ADD_CUSTOM_COMMAND to

Re: [cmake-developers] [PATCH 0/3] FindwxWidgets improvements

Am Dienstag, 19. Januar 2016, 14:25:15 schrieb Brad King: > On 09/09/2015 11:01 AM, Brad King wrote: > > FindwxWidgets: allow specifying required version > > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6089fde5 > > This introduced a regression reported here: > >

Re: [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 5:16 PM, Stephen Kelly wrote: > Taylor Braun-Jones wrote: > >> Consider library project Foo that uses a header-only project Bar. In >> FooConfig.cmake, it is a important to ensure any projects using Foo also >> use the exact same version of Bar that Foo

[Cmake-commits] CMake branch, next, updated. v3.4.2-2023-g683f5b1

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2025-gbde6c55

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

Re: [cmake-developers] BUG: Pass --build-config option to ctest for multi-config ExternalProjects

On 01/19/2016 03:54 PM, Taylor Braun-Jones wrote: > For ExternalProjects built with a multi-config generator like "Visual > Studio 12" with `TEST_BEFORE_INSTALL ON` I need this patch: > > https://github.com/Kitware/CMake/compare/master...nocnokneo:patch-1 > > Otherwise, the test step gives the

[Cmake-commits] CMake branch, next, updated. v3.4.2-2030-gf0f0470

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

Re: [cmake-developers] [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 5:16 PM, Stephen Kelly wrote: > Taylor Braun-Jones wrote: > >> Consider library project Foo that uses a header-only project Bar. In >> FooConfig.cmake, it is a important to ensure any projects using Foo also >> use the exact same version of Bar that Foo

[Cmake-commits] CMake branch, next, updated. v3.4.2-2028-gd1a35c5

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

Re: [cmake-developers] BUG: Pass --build-config option to ctest for multi-config ExternalProjects

On Tue, Jan 19, 2016 at 4:18 PM, Brad King wrote: > On 01/19/2016 03:54 PM, Taylor Braun-Jones wrote: >> For ExternalProjects built with a multi-config generator like "Visual >> Studio 12" with `TEST_BEFORE_INSTALL ON` I need this patch: >> >>

[cmake-developers] BUG: Pass --build-config option to ctest for multi-config ExternalProjects

For ExternalProjects built with a multi-config generator like "Visual Studio 12" with `TEST_BEFORE_INSTALL ON` I need this patch: https://github.com/Kitware/CMake/compare/master...nocnokneo:patch-1 Otherwise, the test step gives the error "Test not available without configuration." Thanks,

Re: [cmake-developers] Access output from CheckCXXSourceRuns and CheckCSourceRuns

On 01/19/2016 12:03 PM, Harry Mallon wrote: > I cannot retrieve a version number without linking and interrogating > the library. I could be missing something though. Are you saying that the only API provided by the package in question to get its version number is a runtime call? There is no

[Cmake-commits] CMake branch, next, updated. v3.4.1-2029-g2610a2b

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

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

We are pleased to announce that CMake 3.4.2 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.2 since 3.4.1: Brad

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

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.2 has been created at e7153bdf97a402eb9b74b3811487b6299c3c441b (tag) tagging

[CMake] [ANNOUNCE] CMake 3.4.2 available for download

We are pleased to announce that CMake 3.4.2 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.2 since 3.4.1: Brad

Re: [cmake-developers] Access output from CheckCXXSourceRuns and CheckCSourceRuns

Yep. The headers are the same version to version but provide a function to retrieve a filled version struct. H Harry Mallon CODEX | Software Engineer 60 Poland Street | London | England | W1F 7NT E ha...@codexdigital.com | T +44 203 7000

Re: [cmake-developers] [PATCH] FindPNG: Create an imported PNG::PNG target

On 01/19/2016 12:43 PM, Sam Thursfield wrote: > Imported targets are now the recommended way of dealing with external > library dependencies. Thanks! Applied with minor doc format fixup and merged to 'next' for testing: FindPNG: Create an imported PNG::PNG target (#15911)

[cmake-developers] [PATCH] FindPNG: Create an imported PNG::PNG target

Imported targets are now the recommended way of dealing with external library dependencies. The documentation for FindPNG is rewritten slightly. This commit also adds a test case, you can run it like this: cmake ... -DCMake_TEST_FindPNG=ON ctest -R FindPNG --output-on-failure The

Re: [cmake-developers] [PATCH] FindALSA: Create an imported ALSA:ASound target

On 01/19/2016 11:50 AM, Sam Thursfield wrote: > Imported targets are now the recommended way of dealing with external > library dependencies. Thanks! Adding Roger Leigh to Cc because he has implemented several of these for other modules. > + set(ALSA_LIBRARIES ${ALSA_LIBRARY}) > +

Re: [cmake-developers] [PATCH 0/3] FindwxWidgets improvements

On 09/09/2015 11:01 AM, Brad King wrote: > FindwxWidgets: allow specifying required version > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6089fde5 This introduced a regression reported here: https://cmake.org/Bug/view.php?id=15928 The version extraction from the header is breaking the

[Cmake-commits] CMake branch, next, updated. v3.4.1-2027-g078e8a2

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-871-gc13ed96

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

[Cmake-commits] CMake branch, release, updated. v3.4.1-13-g6506dca

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

Re: [cmake-developers] [patch] New find module FindXalanC

On 19/01/2016 19:14, Brad King wrote: On 01/19/2016 12:02 PM, Roger Leigh wrote: +find_package(XercesC 3.0.0 REQUIRED) I think this is an assumption leaking from my own usage of it. I've removed the version here. Thanks. The CMakeOnly.AllFindModules and FindModulesExecuteAll tests fail

[Cmake-commits] CMake branch, next, updated. v3.4.2-2032-gda0dd89

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

Re: [CMake] XCode Generation Issue

Any help would be appreciated. In particular I’d like to know how the default compiler arguments are set when ‘cmake -G Xcode’ is executed. The attached file contains the cmake test compile extracted and reformatted from CMakeOutput.log that should have failed. Again, what is setting all the clang

[CMake] Internal error bug in v3.4.2.

I compiled v3.4.2 and after installing it in /usr/local, I tried running it in a project that was working fine with cmake 2.8. I removed cmake2.8 from my computer. I get: -- Buildir /media/Linux/code/applications/mrViewer/BUILD/Linux-3.16.0-57-generic-64/Release cd

Re: [CMake] XCode Generation Issue

On 1/19/16, David Morsberger wrote: > Any help would be appreciated. > > In particular I’d like to know how the default compiler arguments are set > when ‘cmake -G Xcode’ is executed. The attached file contains the cmake test > compile extracted and reformatted from

[cmake-developers] [PATCH] Fix args handling in cmake -E time

>From 7b01d1aed22b16fd81c3ae47dd51311e9a15187a Mon Sep 17 00:00:00 2001 From: wonder-mice Date: Tue, 19 Jan 2016 18:13:10 -0800 Subject: [PATCH] Fix args handling in cmake -E time Previous implementation had two issues: * Quotes in arguments where not escaped * No special

[Cmake-commits] CMake branch, master, updated. v3.4.2-859-g15fe480

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

Re: [CMake] [ANNOUNCE] CMake 3.4.2 available for download

Works well, although I did find that I had to update my Windows SDK to 10.0.10586.0 when using Visual Studio 2015 on Windows 10. This is because CMake detected the system as Windows - 10.0.10586 - AMD64. This was not the case with the previous version of CMake (3.4.1). Andrew > --

Re: [CMake] add_custom_command scope

Am 19. Januar 2016 12:30:39 MEZ, schrieb Lars : > Hello, > >Using CMake 3.3 and VS2012. > >The below cmake scripts generate "Policy CMP0040 is not set: The target >in the TARGET signature of add_custom_command must exists". Why cannot >the custom/CMakeLists.txt file see

[cmake-developers] [CMake 0015926]: FindCURL.cmake exposed variables are empty

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15926 == Reported By:Lars Kühne Assigned To:

[Cmake-commits] CMake branch, master, updated. v3.4.1-867-g249aac7

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-853-g2a73530

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-855-gcaf4985

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-861-g65146af

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-863-gf8f5315

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-857-g790959a

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2005-g29b8a5b

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2003-gd78f9e3

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2007-g5c0d5f0

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

[cmake-developers] [CMake 0015927]: Escape semicolon "; " in CMake/CTest variables?

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2019-gf1bbd97

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

Re: [cmake-developers] [PATCH] Now prints warning when --build is not honored

On 01/17/2016 11:35 AM, Ashley Whetter wrote: > As per issue 12641, this patch means that a warning is given when the > "--build" > option is ignored. Thanks for working on this. > I'm not sure if you'd want a different error message here. Ideally all unused arguments would get a warning but

Re: [cmake-developers] [CMAKE][PATCH] fix create_javah on Windows

On 01/19/2016 03:58 AM, CHEVRIER, Marc wrote: > Attached is a patch fixing erroneous handling of CLASSPATH > Update tests accordingly. Thanks, applied: UseJava: Fix create_javah CLASSPATH handling on Windows https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=18c3714f -Brad -- Powered by

Re: [cmake-developers] [PATCH] Added FILTER subcommand to list command

On 01/16/2016 12:10 PM, Ashley Whetter wrote: > In response to issue 0003986, I've implemented a FILTER subcommand to the > "list" > command that filters a list using a regular expression. Nice work. The change looks good except I'd like to bikeshed the name of the option. This is the first

[Cmake-commits] CMake branch, master, updated. v3.4.1-869-ge4a135d

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2012-g7ebea33a

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

Re: [cmake-developers] [PATCH] Now prints line number of cache parse error

On 01/17/2016 05:09 PM, Ashley Whetter wrote: > To fix issue 11109, this patch implements the printing of the line number of > the > CMakeCache.txt file that causes a parse error when an error occurs. Thanks! Applied with minor fix to the test suite: Print line number of cache parse errors

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 01/18/2016 01:51 PM, Eric Wing wrote: > So the good news is I have a basic add_executable working with Swift > on Linux via the Makefile generator. > > It works with all Swift files, or intermixed C+Swift files. Bridging > header is also supported. Great! > - I’m still copying over some

[Cmake-commits] CMake branch, next, updated. v3.4.1-2009-gab20512

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2015-g6ed6ba6

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

Re: [cmake-developers] Access output from CheckCXXSourceRuns and CheckCSourceRuns

On 01/18/2016 01:32 PM, Harry Mallon wrote: > https://github.com/Kitware/CMake/pull/209 > This passes through the output of the run (as well as the return value) > so that users can access any output without using try_run. Thanks. The signature of the macro takes a variable for the return value

[Cmake-commits] CMake branch, release, updated. v3.4.1-12-g8ce5ff8

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2017-g867a79a

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-2021-g4af8e76

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

[cmake-developers] [patch] New find module FindXalanC

Merged into next from the staging branch "xalanc" for review and testing. Includes a couple of unit tests to validate. Since it depends on XercesC, I hope what I've done here for the imported and non-imported target cases is OK. I've tested on Linux and Windows. Regards, Roger --

[cmake-developers] [CMake 0015928]: FindwxWidgets Fails

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

Re: [cmake-developers] [patch] New find module FindXalanC

On 19/01/2016 16:50, Brad King wrote: On 01/19/2016 11:39 AM, Roger Leigh wrote: Merged into next from the staging branch "xalanc" for review and testing. Includes a couple of unit tests to validate. Since it depends on XercesC, I hope what I've done here for the imported and non-imported

Re: [cmake-developers] [patch] New find module FindXalanC

On 01/19/2016 11:39 AM, Roger Leigh wrote: > Merged into next from the staging branch "xalanc" for review and > testing. Includes a couple of unit tests to validate. Since it depends > on XercesC, I hope what I've done here for the imported and non-imported > target cases is OK. Thanks.

[cmake-developers] [PATCH] FindALSA: Create an imported ALSA:ASound target

Imported targets are now the recommended way of dealing with external library dependencies. The documentation for FindALSA is rewritten slightly. This commit also adds a test case, you can run it like this: cmake ... -DCMake_TEST_FindALSA=ON ctest -R FindALSA --output-on-failure The

Re: [cmake-developers] Access output from CheckCXXSourceRuns and CheckCSourceRuns

Inline responses. Harry Mallon CODEX | Software Engineer 60 Poland Street | London | England | W1F 7NT E ha...@codexdigital.com | T +44 203 7000 989 > On 19 Jan 2016, at 15:42, Brad King wrote: > > On 01/18/2016 01:32 PM, Harry Mallon wrote: >>

[Cmake-commits] CMake branch, next, updated. v3.4.1-2025-g9641548

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