Re: [CMake] Internal error bug in v3.4.2.

On 01/21/2016 07:53 AM, Gonzalo wrote: > I delved into the cmake 3.4.2 source code and found the offending line > in cmTarget.cxx: > > cmSystemTools::ExpandListArgument((*it)->ge->Evaluate(mf, >config, >

Re: [CMake] CMake 3.4.2 available for download

On 01/20/2016 04:36 PM, Andrew Maclean wrote: > "CMake Error at CMakeLists.txt:1 (project): > Could not find an appropriate version of the Windows 10 SDK installed on > this machine" > > In CMakeOutput.log, there is one line: > "The system is: Windows - 10.0.10586 - AMD64" It looks like

[CMake] Adding definitions to compile one file ?

Hi I want to add two definitions to compile one specific files in addition to the global definitions. I have the following problem. If I use set_source_files_properties(source.cpp PROPERTIES COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} ) then I get error message incorrect number of

Re: [CMake] XCode Generation Issue

Eric, I went down a rabbit hole and pulled myself back out. I narrowed it down to the following. We are using cmake to check if the linker supports -Wl,—as-needed. The test compile (and link?) command cmake builds using ‘cmake -G Xcode’ does not fail. The command from ‘cmake -G’ has been

Re: [CMake] Internal error bug in v3.4.2.

El 20/01/16 a las 15:51, Brad King escribió: It's not gone or even deprecated. It's just not well tested and seems to be broken in your particular case in a way not reproduced by the test. I delved into the cmake 3.4.2 source code and found the offending line in cmTarget.cxx:

Re: [CMake] Customizing output of ctest command

I would also be very much interested how this could be done. There was a thread I started a few months ago on a similar topic. I wanted to see the execution times of various tests without the initialization part. If my tests could output in some form the useful part of their run times, it

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Ah, I ran into this quirk too - the issue is that you have the quotes incorrect: -DCMAKE_CXX_FLAGS="-march=native" Should be like this instead: "-DCMAKE_CXX_FLAGS=-march=native" Try that and see if it helps, I am pretty sure I ran into the exact same problem. On Thu, Jan 21, 2016 at 8:27 AM,

[CMake] Re : Re: Re : Re: Re : Re: How to pass a configuration file to CMake?

Thank you Chuck & Petr! It works fine now! :) Cédric - Chuck Atkins a écrit : >CMake strongly encourages the use of separate source and build directories >(unlike autotools). So, try something like this: mkdir build cd build cmake -C

Re: [CMake] Adding definitions to compile one file ?

HI Petr Thanks for the suggestion. But this will erase the existing compile definitions, won't it ? So may be I should do a get_property first, append my new definitions and reset the property ? I'll try anyway... Vania On 01/21/2016 03:21 PM, Petr Kmoch wrote: Hi Vania. For your case, it's

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Thanks for clarifying that external projects are not aware of the project they are embedded in. The CMAKE_COMPILER_IS_GNUCXX variable should be set automatically by CMake as far as I understand it (see https://cmake.org/Wiki/CMake_Useful_Variables). I narrowed down the problem by creating a

Re: [CMake] Adding definitions to compile one file ?

On Thu, Jan 21, 2016 at 3:26 PM, Vania Joloboff wrote: > HI Petr > > Thanks for the suggestion. > But this will erase the existing compile definitions, won't it ? > So may be I should do a get_property first, > append my new definitions and reset the property ? > I'll

Re: [CMake] How to pass a configuration file to CMake?

Hi Cedric, The option can be a bit confusing. The cache file you pass is actually a CMake script that sets cache variables, rather than the cache variables as seen in CMakeCache.txt. So you would actually want your cache file to contain: set(CMAKE_BUILD_TYPE Debug CACHE STRING "Choose the type

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Nice, thank you very much! This solves my problem. On Thu, Jan 21, 2016 at 3:56 PM, Nicholas Braden wrote: > Ah, I ran into this quirk too - the issue is that you have the quotes > incorrect: > > -DCMAKE_CXX_FLAGS="-march=native" > > Should be like this instead: > >

Re: [CMake] Adding definitions to compile one file ?

2016-01-21 15:14 GMT+01:00 Vania Joloboff : > Hi > > I want to add two definitions to compile one specific files > in addition to the global definitions. > I have the following problem. If I use > > set_source_files_properties(source.cpp > PROPERTIES > COMPILE_DEFINITIONS

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Thanks for your suggestion! I consider trying it soon. On Wed, Jan 20, 2016 at 11:44 PM, Craig Scott wrote: > > From: fkillus >> To: cmake@cmake.org >> Cc: >> Date: Wed, 20 Jan 2016 18:41:26 +0100 >> Subject: [CMake] ExternalProject_Add() macro

Re: [CMake] Adding definitions to compile one file ?

Use APPEND keyword: set_property( SOURCE source.cpp APPEND PROPERTY COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} ) On 21/01/16 15:26, "CMake on behalf of Vania Joloboff" wrote: >HI Petr > >Thanks for the

Re: [CMake] Adding definitions to compile one file ?

Hi Vania. For your case, it's best to forget about the not-as-convenient-as-they-could-be convenience functions set_*_properties, and just invoke set_property: set_property( SOURCE source.cpp PROPERTY COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} ) Petr On Thu, Jan 21, 2016 at

[CMake] Re : Re: How to pass a configuration file to CMake?

Hello, I do not manage to pass a configuration file to cmake. I type 'cmake -C ../config.cmake' where config.cmake belongs to the parent directory and contains these lines: set(ENABLE_DOWNLOAD True CACHE BOOL) set(GCC_ROOT "/local/cdoucet/gcc/4.9.2/" CACHE PATH) I get the following error

Re: [CMake] How to pass a configuration file to CMake?

Hi Cedric. I believe the comment string argument is mandatory in a set(... CACHE), so it should be something like this: set(ENABLE_DOWNLOAD True CACHE BOOL "Should download be enabled") set(GCC_ROOT "/local/cdoucet/gcc/4.9.2/" CACHE PATH "Path to root directory of GCC installation") Petr On

[CMake] Re : Re: Re : Re: How to pass a configuration file to CMake?

Hi Petr, thank you very much for your answer! Indeed, comment string arguments seem to be mandatory. I modified my configuration file like this: set(ENABLE_DOWNLOAD True CACHE BOOL "Automatic installation of third-party libraries") set(GCC_ROOT "/local/cdoucet/gcc/4.9.2/" CACHE PATH "Root of

Re: [CMake] How to pass a configuration file to CMake?

CMake strongly encourages the use of separate source and build directories (unlike autotools). So, try something like this: mkdir build cd build cmake -C /path/to/SuperCoolCacheFile.cmake /path/to/source - Chuck On Thu, Jan 21, 2016 at 10:10 AM, Cedric Doucet wrote:

Re: [CMake] Adding definitions to compile one file ?

Hi, On 21/01/16 15:14, Vania Joloboff wrote: Hi I want to add two definitions to compile one specific files in addition to the global definitions. I have the following problem. If I use set_source_files_properties(source.cpp PROPERTIES COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} )

Re: [CMake] Creating RPMs from failing projects with CPack

Hi Domen, Thanks a lot for the tip! I'll give it a try. (The "monolithic limitation" should not be an issue for us. We do build single RPMs for our projects.) Cheers, Attila > On 21 Jan 2016, at 00:49, Domen Vrankar wrote: > >> I have a slightly unusual

Re: [CMake] How to pass a configuration file to CMake?

It looks as if CMake was interpreting the path as both the source directory and the initial cache file. Perhaps you could help it by adding the path to source explicitly: cmake -C ../config.cmake whatever/your/path/to/source/is Petr On Thu, Jan 21, 2016 at 4:10 PM, Cedric Doucet

Re: [CMake] Internal error bug in v3.4.2.

Thanks. This is consistent with the call stack shown in your original post. That line is always executed so we need to figure out what goes wrong with it in your particular case. Since you can reproduce it in mrViewer's configuration that is a good starting point. Try removing sources and

Re: [CMake] Internal error bug in v3.4.2.

El 21/01/16 a las 10:28, Brad King escribió: Thanks. This is consistent with the call stack shown in your original post. That line is always executed so we need to figure out what goes wrong with it in your particular case. Since you can reproduce it in I forgot to mention. FLTK2.0 is

Re: [CMake] How to pass a configuration file to CMake?

Hi Cedric, I believe you should do it this way: Your config.cmake file should be: set(ENABLE_DOWNLOAD True CACHE BOOL "") set(GCC_ROOT "/local/cdoucet/gcc/4.9.2/" CACHE PATH "") In the signature of set() for "Set Cache Entry", the *docstring* is mandatory. cf

Re: [CMake] Internal error bug in v3.4.2.

On 01/21/2016 11:00 AM, Gonzalo wrote: > Find attached the mrViewer/src/CMakeList.txt file that still fails. Thanks. From that I was able to reproduce it in a small test case with CMake 3.4. It appears that the problem has been fixed since then in 'master'. I've added a test case to keep it

Re: [CMake] Internal error bug in v3.4.2.

On 21/01/2016 03:47 p.m., Brad King wrote: On 01/21/2016 11:00 AM, Gonzalo wrote: Find attached the mrViewer/src/CMakeList.txt file that still fails. Thanks. From that I was able to reproduce it in a small test case with CMake 3.4. It appears that the problem has been fixed since then in

Re: [CMake] ExternalProject not being configured / custom_command not executed

On 1/21/2016 2:33 PM, Kügler, David wrote: Hello everybody, I am trying to build a Project (via ExternalProject from a parent project). More precisely, I want to build the plus Toolkit (plustoolkit.org) and the subprojects using the build “superproject” (i.e. PlusBuild). It partly seems to

Re: [CMake] XCode Generation Issue

On 1/21/16, David Morsberger wrote: > Eric, > > I went down a rabbit hole and pulled myself back out. I narrowed it down to > the following. > > We are using cmake to check if the linker supports -Wl,—as-needed. The test > compile (and link?) command cmake builds using ‘cmake

Re: [CMake] CMake 3.4.2 available for download

Thanks for this Brad, your comments in https://cmake.org/Bug/view.php?id=15929#c40287 make it very clear as to what is happening. I had naively assumed that when installing a new Visual Studio compiler that the latest SDK would be also installed! It is nice to see that CMake 3.4.2 does the checks

[CMake] ExternalProject not being configured / custom_command not executed

Hello everybody, I am trying to build a Project (via ExternalProject from a parent project). More precisely, I want to build the plus Toolkit (plustoolkit.org) and the subprojects using the build "superproject" (i.e. PlusBuild). It partly seems to work fine, but the ExternalProject PlusApp

Re: [CMake] Internal error bug in v3.4.2.

El 21/01/16 a las 15:47, Brad King escribió: Thanks. From that I was able to reproduce it in a small test case with CMake 3.4. It appears that the problem has been fixed since then in 'master'. I've added a test case to keep it working: I confirm the bug is squashed in master!

[Cmake-commits] CMake branch, next, updated. v3.4.2-2065-g1ca1451

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

Re: [cmake-developers] CMake daemon for user tools

On 01/20/2016 04:03 PM, Stephen Kelly wrote: > FYI I merged a reduce-allocations branch to next for testing. It came from > Milian here: > > https://github.com/steveire/CMake/pull/1 Very nice! Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake

[cmake-developers] [CMake 0015930]: MSVC project switched to Windows XP toolset won't compile

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

[cmake-developers] [PATCH V2] 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

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

Updated to refer to ZLIB::ZLIB, and with documentation tweak. Sam Thursfield (1): FindPNG: Create an imported PNG::PNG target Help/release/dev/FindPNG-imported-targets.rst | 4 +++ Modules/FindPNG.cmake | 50 +++ Tests/CMakeLists.txt

[Cmake-commits] CMake branch, next, updated. v3.4.2-2070-gaa6eaa6

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

[cmake-developers] [CMake 0015931]: Change the StartUp-Solution by Value

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2072-g92b073f

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

Re: [cmake-developers] [PATCH] Fix crash in cmExportInstallFileGenerator::FindNamespaces()

On 01/20/2016 09:41 PM, Andrey Pokrovskiy wrote: > Subject: [PATCH] Fix crash in cmExportInstallFileGenerator::FindNamespaces() > > Found it when was building poco library: > https://github.com/pocoproject/poco.git > > Steps to reproduce: > 1. Clone poco > 2. mkdir poco.git/build.make > 3. cd

[Cmake-commits] CMake branch, master, updated. v3.4.2-890-g3e7794a

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2078-gf559b68

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-884-gaaf06f2

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-880-g071c94e

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-882-g563a6c7

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-877-g1846765

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2080-gd194d14

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

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

On 01/21/2016 11:46 AM, Sam Thursfield wrote: > Imported targets are now the recommended way of dealing with external > library dependencies. Thanks, re-applied and merged to 'next' for testing: FindPNG: Create an imported PNG::PNG target (#15911)

[Cmake-commits] CMake branch, next, updated. v3.4.2-2068-g8ef9c76

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

[cmake-developers] [CMake 0015932]: Path too long installing from installer

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

Re: [cmake-developers] CMake daemon for user tools

On Wed, Jan 20, 2016 at 10:03 PM, Stephen Kelly wrote: > Milian Wolff wrote: > >>> I'm concerned that the memory usage of a daemon implementing the proposed >>> capabilities may be too large to be practical (at least without a major >>> redesign of certain structures that tend

[Cmake-commits] CMake branch, master, updated. v3.4.2-891-gf81ccc5

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