[CMake] Announcing CMake BASIS, a set of CMake based project interoperability and automation tools

CMake BASIS is a set of utilities and standards created with the goal of making CMake projects and libraries very easy to create, share, and reuse. It also integrates a lot of useful new CMake functionality such as documentation tools and automated packaging that a CMake user would otherwise have t

Re: [CMake] export(TARGETS for multi-configuration

-- Message: 2 Date: Fri, 17 Jan 2014 23:46:45 +0400 From: ZZ ZZ To: cmake@cmake.org Subject: [CMake] export(TARGETS for multi-configuration Message-ID: <176711389988...@web18h.yandex.ru> Content-Type: text/plain; charset=koi8-r Hi all, Our CMakeLists.txt contains wi

Re: [CMake] Why is -fPIE added to my build?

Yes, that's it, thank you! I thought the flag only affects library builds, but apparently not. Michael On Jan 21, 2014, at 10:20 , Nils Gladitz wrote: > On 01/21/2014 10:05 AM, Schlottke, Michael wrote: >> >> However, I noticed that CMake adds the '-fPIE' flag to the compilation >> flags with

Re: [CMake] Why is -fPIE added to my build?

On 01/21/2014 10:05 AM, Schlottke, Michael wrote: However, I noticed that CMake adds the '-fPIE' flag to the compilation flags without me asking for it. Maybe there is a set(CMAKE_POSITION_INDEPENDENT_CODE ON) in the project or the POSITION_INDEPENDENT_CODE property is set for the target itse

[CMake] Why is -fPIE added to my build?

Hi everyone, We use CMake to create the build files for our C++ research code. We compile all source files directly into one executable and then link statically to a couple of external libraries. However, I noticed that CMake adds the '-fPIE' flag to the compilation flags without me asking for