Re: [CMake] CTest threshold exceeds 1024 bytes

On 07/21/2015 06:16 PM, Roman Wüger wrote: I've attached a patch which learns CTest to handle it. I hope this patch could be merged. Good start. Please also update Help/manual/ctest.1.rst with documentation for the new options. Also please extend the test suite, likely in

[CMake] Changes to CMAKE_CXX_FLAGS_RELEASE not reflected in GUI

Dear CMake Community, I would like to add an extra flag to CMAKE_CXX_FLAGS_RELEASE (-xHost for Intel compilers), so in my CMakeLists.txt I add: set( CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE} -xHost ) If I then run VERBOSE=1 make, I observe that the xHost flag is passed to the compiler.

Re: [CMake] config-specific compiler definitions don't work properly

Hi: It solved the compiler definitions. However, when I come to work with library, it came with further errors. In my project, we have an extra configuration named GraphicDebug. I want to have my project to use different library files which are compiled using different options. Firstly I

Re: [CMake] Linking error after having found a package

I'm afraid you're right. :-/ It works fine now. Thank you very much Eric! - Mail original - De: Eric Noulard eric.noul...@gmail.com À: Cedric Doucet cedric.dou...@inria.fr Cc: cmake@cmake.org Envoyé: Mercredi 22 Juillet 2015 14:31:22 Objet: Re: [CMake] Linking error after having

[CMake] Linking error after having found a package

Hello, I try to use the find_package function to find BLAS and LAPACK libraries which are required in my code. To do that, I do the following: == FIND_PACKAGE(BLAS) FIND_PACKAGE(LAPACK) # I should test with BLAS_FOUND and LAPACK_FOUND here but that's not the

Re: [CMake] Visual Studio solution folders with 1 item in them

globally set set_property(GLOBAL PROPERTY USE_FOLDERS On) SET_TARGET_PROPERTIES(target PROPERTIES FOLDER folder name ) On Wed, Jul 22, 2015 at 3:04 PM, Andrei Porumb anpor...@microsoft.com wrote: Hello CMake, Thank you for everything so far!

Re: [CMake] Visual Studio solution folders with 1 item in them

What you are suggesting will add some previously build targets to the solution inside a solution folder. What I want is to simply have a file inside a solution folder. Best Regards, Andrei Porumb a skhizein equals to 1 software rename/dev cycle From: J Decker [mailto:d3c...@gmail.com] Sent:

Re: [CMake] Fortran build dependency on Windows

Consider this issue closed - all Nightly tests succeeded. Thank You very much! Allen On Tuesday, July 21, 2015 04:17:39 PM Brad King wrote: On 07/21/2015 01:06 PM, Brad King wrote: It looks like OBJECT_DEPENDS is not fully implemented for VS = 10. I'll look at fixing that. It turns

Re: [CMake] find_package and lib/cmake/Foo

Robert Have you tried setting CMAKE_PREFIX_PATH That seems to work. I will use it from now on. Thanks JB -- 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

Re: [cmake-developers] Listing source-tree files encountered

On 07/21/2015 12:33 PM, Brad King wrote: I'll take a look at this when I get a chance. Applied, thanks: Add SOURCE_DIR and BINARY_DIR target properties http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=45c5f8ca There is some coverage of the SOURCES property in other tests but having a

Re: [cmake-developers] Patch for FindBZip2.cmake BZIP2_NEED_PREFIX issue with cross compiled mingw32 applications

On 07/21/2015 12:10 PM, Ralf Habacker wrote: updated patch appended Applied, thanks: FindBZip2: Check BZIP2_NEED_PREFIX with real prototype http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=23876eda -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1252-g1a536bf

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1259-g47aeac3

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

Re: [cmake-developers] Is this warning really needed: You have called ADD_LIBRARY for library foobar without any source files.?

On 07/22/2015 08:25 AM, Erik Sjölund wrote: I think this warning could be removed: You have called ADD_LIBRARY for library foobar without any source files. This typically indicates a problem with your CMakeLists.txt file Yes, since we started allowing sources to be modified after the call

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-525-g4c3d431

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

Re: [cmake-developers] [CMake] CTest threshold exceeds 1024 bytes

On 07/21/2015 06:16 PM, Roman Wüger wrote: I've attached a patch which learns CTest to handle it. I hope this patch could be merged. Good start. Please also update Help/manual/ctest.1.rst with documentation for the new options. Also please extend the test suite, likely in

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-523-g90b3b5e

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

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-528-ge00e871

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1261-g9cb0ac1

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1270-g9a35857

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1276-gc7bc8c0

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1278-gb90298c

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1241-ge4097bf

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

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-521-g5967803

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1245-gc3a1c82

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

[Cmake-commits] CMake branch, release, updated. v3.3.0-rc4-4-gb9fba34

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1247-g5b4c1f2

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

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-529-g900554b

20150722) +set(CMake_VERSION_PATCH 20150723) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake

[cmake-developers] [CMake 0015659]: Visual Studio 2015: check_function_exists doesn't work for stdio functions

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15659 == Reported By:Alex Lamaison Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1250-g97cf80f

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-rc4-1255-g4ef5c6a

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

[cmake-developers] Is this warning really needed: You have called ADD_LIBRARY for library foobar without any source files.?

Hi, I think this warning could be removed: You have called ADD_LIBRARY for library foobar without any source files. This typically indicates a problem with your CMakeLists.txt file If you have a function that populates sources to a target, let us say something like this:

[Cmake-commits] CMake branch, master, updated. v3.3.0-rc4-518-g02e5eba

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