[cmake-developers] fix-install-rules topic fix for 3.4

Steve, I've queued this change: Install: Move SetHaveInstallRule to a more-obvious place https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9103d8ac for merge to the 'release' branch for 3.4. What were the observed effects of this regression? Thanks, -Brad -- Powered by www.kitware.com

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1279-g8f876df

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

Re: [CMake] WIX installer fails for shared files

On 11/06/2015 08:06 PM, Mark Stijnman wrote: install(FILES 1.txt common.txt DESTINATION bin COMPONENT comp1) install(FILES 2.txt common.txt DESTINATION bin COMPONENT comp2) CMake does not implement any diagnostics that would prevent you from doing so but installing distinct files (or even

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1283-g113cd68

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

[cmake-developers] [CMake 0015838]: CPack WIX generator should set top feature to be mandatory

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15838 == Reported By:Mark Stijnman Assigned To:

Re: [cmake-developers] Add command line options for deprecation message control

On 11/06/2015 05:31 PM, Michael Scott wrote: >> increments the count by default instead of only when an explicit >> option has been set. Please revise accordingly based on the attached >> state. > I don't quite follow. Setting "dev" to DIAG_WARN in DiagLevels, before > the users input is parsed

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-492-ged48454

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-501-g0ecb5e7

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-499-g9ad0ae1

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1289-gb5ff9b5

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-490-g20e445f

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1272-ge9dda56

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

Re: [cmake-developers] Adding Ninja file dependency to ExternalProject target

On 11/06/2015 05:16 PM, Chris Bieneman wrote: > external project will have a file-dependency on clang? >From a quick check it looks like ExternalProject has no interface to directly add file-level dependencies to the builtin configure step. That should be corrected if anyone is interested in

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1281-gee7fc8b

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

Re: [cmake-developers] Add command line options for deprecation message control

The goal of the old logic was to avoid populating the settings in the cache if they are left as default. Instead you could check whether any "dev" value has been set *after* parsing the options and if not then set it to the default. Ah okay I understand, that's no problem. I've pretty much

Re: [CMake] [ANNOUNCE] CMake 3.4.0-rc1 is now ready!

On 2015-10-22 13:30-0400 Brad King wrote: [...] Plplot's Ada support uses CMake internal APIs so it is plplot's responsibility to adapt to our changes: [...] Where Plplot currently writes: SET(CMAKE_Ada_COMPILE_OBJECT " -c -o ") try: if(NOT CMAKE_VERSION VERSION_LESS 3.4)

Re: [CMake] Fwd: Re: cmake needs 2 runs to find boost

On Mon, 9 Nov 2015, Andreas Naumann wrote: Did boost change the naming convention? The documentation says, it should be named with vc. And therefore, cmake cannot find the library... Even the boost header files rely on the names in Visual studio. So, I would assume, your boost installation to

[cmake-developers] IAR Workbench extra generator

Hello cmake-developers! I spent couple of days adding IAR Workbench generator for ARM into CMake. Locally, it has all features I originally wanted, and I thought of giving the patch to everyone. The problem is, I do not know about the standards for making such generator, e.g. CMake coding

Re: [CMake] Fwd: Re: cmake needs 2 runs to find boost

Did boost change the naming convention? The documentation says, it should be named with vc. And therefore, cmake cannot find the library... Even the boost header files rely on the names in Visual studio. So, I would assume, your boost installation to be broken? Regards, Andreas Am 09.11.2015

[cmake-developers] [CMake 0015839]: Create src.rpm package

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15839 == Reported By:Egor Shokhin Assigned To:

Re: [cmake-developers] Adding Ninja file dependency to ExternalProject target

Hi Brad, Thanks for the recommendation. I’ll give it a try today. -Chris > On Nov 9, 2015, at 6:29 AM, Brad King wrote: > > On 11/06/2015 05:16 PM, Chris Bieneman wrote: >> external project will have a file-dependency on clang? > > From a quick check it looks like

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1291-g377027b

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

Re: [CMake] WIX installer fails for shared files

Hi Nils, thanks for the reply. On Mon, Nov 9, 2015 at 4:09 PM, Nils Gladitz wrote: > CMake does not implement any diagnostics that would prevent you from doing > so but installing distinct files (or even the same file multiple times) to > the same destination path is ill

Re: [CMake] Ctest executable dll/so search path

The solution I came up with was the following.. SET_TESTS_PROPERTIES( ${TEST_NAME} PROPERTIES ENVIRONMENT "PATH=${TCL_BINDIR};$ENV{PATH}" ) It worked like a charm. Scott -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Iosif Neitzke Sent: Sunday,

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-502-g21684a2

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

Re: [cmake-developers] [CPackDeb] Configure Debian package name for components

My too fast read of your patch and message make me think that the issue was about the file name. Now I understand. No problem, I know the CPack generated file names are a long-standing issue. Indeed these seem to be two separate issues. I've applied your patch for CPACK_DEBIAN__PACKAGE_NAME

[CMake] Benchmarking with CMake

Hi! Can anyone tell me if CMake (or CTest) can be customized in a way to produce decent benchmark output? An .xlsx perhaps, or something GnuPlot friendly? I have not found any examples of CTest being (ab)used in this way. Is my feeling correct, that this should be something like CBench?

Re: [CMake] Fwd: Re: cmake needs 2 runs to find boost

I'm actually hitting a similar problem -- I know I've got boost_system installed in c:\dev2\i\lib\boost_system-vc-mt-1_55.dll c:\dev2\i\lib\boost_system-vc-mt-1_55.lib I run cmake like this: cmake ..\krita -G"Visual Studio 14 Win64" -DBoost_DEBUG=ON -DBoost_FIND_QUIETLY=FALSE

Re: [cmake-developers] [CPackDeb] Configure Debian package name for components

2015-11-08 20:01 GMT+01:00 Markus Rickert : > This is a long standing issue with related bugs: >> http://public.kitware.com/Bug/view.php?id=12997 >> http://public.kitware.com/Bug/view.php?id=12574 >> http://public.kitware.com/Bug/view.php?id=11050 >>