Re: [CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

eneral idea as how to approach this: - make a clean cmake directory and try again, or at least remove the CMakeCache.txt - if you use the make generator, add -DCMAKE_VERBOSE_MAKEFILE=ON when calling cmake to know what exactly is being used during build HTH, Jan Hegewald -- Powered by www.kitwar

[CMake] cmake generated Xcode projects are excluded from Time Machine

of the com_apple_backup_excludeItem, the entire yadda directory will be excluded from Time Machine backups. I often tweak the Xcode project as I work with it, change compiler settings, add targets etc. I definitely want this to be in my backup. What do you think? Regards, Jan Hegewald, Climate Sciences, awi.de

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Hi Muhammad, > On 08.03.2016, at 19:12, Muhammad Osama wrote: > > Hi Jan, > > Thank you for your reply, I am in the similar situation, have a very similar > implementation using target_*** but since I don't do that for ALL the > dependencies, I am unable to cmake or

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Hi Muhammad, > On 08.03.2016, at 06:17, Muhammad Osama wrote: > > Hi, I am new to cmake and really hope am doing this correctly. I asked > stackoverflow but didn't get a good enough answer for my specific problem > here; > > If I want root/sub-directories/ as separate

[CMake] install to CMAKE_BINARY_DIR fails if CC=icc

Dear CMakers, I encountered a strange problem with my cmake setup: In my CMakeLists.txt files there is a line install(TARGETS ${PROJECT_NAME} DESTINATION ${CMAKE_BINARY_DIR}) Some of my projects use add_subdirectory, and with make install I "pull" them right to the build directory. This used to

[CMake] COMPILER_LOADED vs ENABLED_LANGUAGES

Hi all, I stumbled upon a problem where a find module did tests via "check_function_exists". It first checks if C is enabled via the ENABLED_LANGUAGES. Now this does not seem to be reliable, as the project language is not C, but C is enables by a project included via add_subdirectory. Now

Re: [CMake] empty list evaluates to false?

Hi Petr, > On 29.02.2016, at 15:27, Petr Kmoch wrote: > > Hi Jan. > > No, that's not possible. Internally, CMake does not differentiate between > "list" and "string" in any way. OK, thanks for the clarification. Best, Jan -- Powered by www.kitware.com Please keep

[CMake] empty list evaluates to false?

Hi cmakers, can I create an empty list which evaluates to true? The way I tried they evaluate to false: set(BLAS_LIBRARIES "") # trying to create an empty list if(BLAS_LIBRARIES) # not called endif() Cheers, Jan -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [CMake] compiler independent compiler flags

> On 17.02.2016, at 11:23, Nagy-Egri Máté Ferenc via CMake > wrote: > > Sorry I could not help, but I do feel the struggle. LOL, yes. Struggle might be the right term. Best, Jan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[CMake] compiler wrappers and linking libraries

Dear all, on a system with a cray compiler environment cmake fails to find a blas capable library via find_package(BLAS) The compilers on this system are wrappers which already link the local blas libraries (from the cray-libsci library). I guess this is why a call to

[CMake] compiler independent compiler flags

Dear all, do you know a best practice on how to specify compiler flags without knowing in advance which compiler will be used? Its about Fortran projects, where I e.g. want to explicitly enable the preprocessor, or make all default real values 8 byte wide. This could be done as such:

Re: [CMake] globs case sensitivity depends on platform

Hi Andreas, thanks for bearing with me (-: > On 28.01.2016, at 20:28, Andreas Pakulat <ap...@gmx.de> wrote: > > Hi Jan, > > On Thu, Jan 28, 2016 at 4:52 PM,  Jan Hegewald <jan.hegew...@awi.de> wrote: > Hi Andreas, > > > On 28.01.2016, at 16:4

Re: [CMake] globs case sensitivity depends on platform

Hi Andreas, > On 28.01.2016, at 16:43, Andreas Pakulat <ap...@gmx.de> wrote: > > Hi Jan, > > On Thu, Jan 28, 2016 at 2:35 PM,  Jan Hegewald <jan.hegew...@awi.de> wrote: > Hi Nils, > > > On 28.01.2016, at 13:39, Nils Gladitz <nilsglad...@gmail.com&

[CMake] globs case sensitivity depends on platform

Hi all, I have some trouble with file globbing using the glob command like so: file(GLOB all_sources ${src_home}/*.F**) the src_home contains files with uppercase and also some with lowercase suffixes, e.g. .F and .f (This makes an important difference to some Fortran compilers regarding

Re: [CMake] globs case sensitivity depends on platform

Hi Nils, > On 28.01.2016, at 13:39, Nils Gladitz wrote: > > You might already be aware but CMake discourages using GLOB for source files yes, I read the docs before posting (: Avoiding glob would be a workaround to my problem. But anyway I think that glob is broken if