Re: [CMake] Parsing command line arguments from the make

I ended up using this exact approach with addition of one top level Makefile which is used to run cmake in build folder. Top level Makefile takes those arguments and passes them down to the cmake execution, which than makes a decision on which way to go depending on the argument passed in. Here

[CMake] Finding all the libraries except for one located in the last path dir

Hello I am calling find_library in a loop, using the same variable for HINTS. This variable (lib_dirs) is set using a script, and when I simply print it using message(), I obtain this output: message(${lib_dirs})

Re: [CMake] Finding all the libraries except for one located in the last path dir

On 05.04.2016 23:31, Salazar De Troya, Miguel wrote: with no line break, whereas the output variable lib_dirs: message(${lib_dirs})

Re: [CMake] Finding all the libraries except for one located in the last path dir

My apologies, the previous error was because of a trailing whitespace. Although I would still like to know why the terminal variable

Re: [CMake] Finding all the libraries except for one located in the last path dir

I resolved this using the option OUTPUT_STRIP_TRAILING_WHITESPACE in execute_process(). https://cmake.org/cmake/help/v3.0/command/execute_process.html I had not seen it. From: Miguel Salazar > Date: Tuesday, April 5, 2016 at 2:31 PM To:

Re: [CMake] Finding all the libraries except for one located in the last path dir

Sorry for the spam, but I found out that there is a line break added by CMake execute_process(COMMAND bash "../grab_libraries.sh" "lib_dirs" "${METHOD}" OUTPUT_VARIABLE lib_dirs) grab_libraries.sh is located in the same folder than CMakeLists.txt and I call cmake .. from a build folder

[CMake] Performance issues on very large project

All, I am currently working on a very large project that contains over 500 (yes, really) listfiles. A co-worker was looking into some performance issues we were seeing during configuration and found something very interesting. Currently configuration is taking 1m57s across several configurations

[CMake] Check the existence of a header / ability to compile source file

Dear All, I'm stumped on the following, seemingly simple issue. I need to figure out in my configuration whether a given header file will be available when I'll try to build my library, or not. So that I could set a particular definition for the compiler according to whether the file is

Re: [CMake] Parsing command line arguments from the make

Hi Fedja, As far as I know, the Makefiles generated from CMake cannot contain decisions. CMake supports several output types aside from Makefiles and some of them probably don’t support decisions. However, you could supply these arguments within CMake call using -D option. For example

Re: [cmake-developers] [PATCH] Fix CMAKE_Fortran_PLATFORM_ID on mingw-w64

On 04/05/2016 04:48 AM, melven.roehrig-zoell...@dlr.de wrote: > Requested changes from Ben Boeckel, > also adjusted the similar if("${...}" MATCHES ...) statements in the section > above. Thanks. Applied: CMakeDetermineFortranCompiler: Modernize conventions

Re: [cmake-developers] CMake API for warnings

On 03/31/2016 12:47 PM, Ruslan Baratov wrote: > What about 3 properties containing list of 's (groups > unexpanded): > > * COMPILE_WARNINGS_DISABLE # e.g. "shift-sign-overflow;unused" > * COMPILE_WARNINGS_ENABLE # e.g. "ALL" > * COMPILE_WARNINGS_TREAT_AS_ERROR # e.g. group + specific:

[Cmake-commits] CMake branch, master, updated. v3.5.1-383-g25a38ec

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-381-gb66a247

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-816-g576f741

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-818-g42c8dec

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-804-gdd68821

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-388-gfd40b0f

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-379-gadea45e

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

Re: [cmake-developers] for C# language support

On 04/04/2016 04:08 PM, Adam Treat via cmake-developers wrote: > I have been working on improving the cmake language module for C# found here: Thanks for working on this. I'm adding Michael Stuermer to Cc who has been working on support in the VS IDE generators:

[Cmake-commits] CMake branch, next, updated. v3.5.1-810-g0b329ba

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-390-g73efdd4

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

Re: [cmake-developers] [PATCH v2] language detection in FindBLAS and FindLAPACK (#0016039)

On 04/03/2016 05:21 PM, melven.roehrig-zoell...@dlr.de wrote: > Updated patch for a problem with find_package(BLAS/LAPACK) > on Windows for pure Fortran projects. > Now simply uses CMAKE__COMPILER_LOADED... Thanks! Applied: Find{BLAS,LAPACK}: Fix when used in pure Fortran projects (#16039)

[Cmake-commits] CMake branch, next, updated. v3.5.1-823-g5ddcbbb

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

Re: [cmake-developers] CMake API for warnings

On 05-Apr-16 21:03, Brad King wrote: On 03/31/2016 12:47 PM, Ruslan Baratov wrote: What about 3 properties containing list of 's (groups unexpanded): * COMPILE_WARNINGS_DISABLE # e.g. "shift-sign-overflow;unused" * COMPILE_WARNINGS_ENABLE # e.g. "ALL" * COMPILE_WARNINGS_TREAT_AS_ERROR # e.g.

[cmake-developers] [CMake 0016049]: Resources generated with autorcc are always rebuilt using ninja

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16049 == Reported By:Vidar Meland Ødegård Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.1-821-g70ae13e

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-826-g1fb6c13

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-391-g8898a92

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

[cmake-developers] [PATCH] Fix CMAKE_Fortran_PLATFORM_ID on mingw-w64

Requested changes from Ben Boeckel, also adjusted the similar if("${...}" MATCHES ...) statements in the section above. Regards Melven -- Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR) German Aerospace Center Simulation and Software Technology | Linder Hoehe |

Re: [cmake-developers] ninja/make compilation response file

Just checked the size that we are getting, it's 20 Mb for all Makefile and *.make combined, and 84 mb build.ninja From: Nils Gladitz [mailto:nilsglad...@gmail.com] Sent: Monday, April 4, 2016 18:57 To: Dmitry Ivanov ; cmake-developers@cmake.org Subject: Re:

Re: [cmake-developers] ninja/make compilation response file

>Teaching the Ninja generator about response files for object file compilation >would be the way to go (and support for RC as well would be good since the >logic is likely the same). I will time box it and see if I can do it in few days, if not we need to figure out if it can be done like a