[CMake] CMP0093 behaviour

Hello, I’m experiencing an odd problem where no matter how I set CMP0093, it seems to use the ‘NEW’ behaviour, breaking some other code relying on the OLD behaviour. This is Cmake 3.15.4 from Homebrew, other people do report on other platforms do report the policy working for them. Here’s my

Re: [CMake] Computation of CMAKE_OSX_SYSROOT

> On 1 Oct 2018, at 14:25, Craig Scott wrote: > > You need to set CMAKE_OSX_DEPLOYMENT_TARGET as a cache variable before > calling the project() command. If you set it as a normal (i.e. non-cache) > variable, the compiler detection logic triggered by the project() call > creates a cache

[CMake] Computation of CMAKE_OSX_SYSROOT

Hi, The docs here: https://cmake.org/cmake/help/v3.12/variable/CMAKE_OSX_SYSROOT.html state that CMAKE_OSX_SYSROOT is computed from CMAKE_OSX_DEPLOYMENT_TARGET if not explicitly set. Can anyone comment on how this works, because in my setup it seems to be failing. This showed up as

[CMake] Force configure_file to re-run

Hi, I was wondering if the official advice on re-running ‘configure_file’ has evolved? There’s some answers on StackOverflow about using custom targets / commands to force it but they seem … ugly. Essentially I want configure_file to re-run each build - I still want the ‘only update the

Re: [CMake] Understanding constraint graph cycles

> On 4 Sep 2017, at 18:37, Robert Maynard wrote: > > Yes you are correct the issue is related to rpath. When CMake constructs the > rpath for the library linking it will have two paths ( > /home/jenkins/workspace/FlightGear/dist/lib64, >

[CMake] Understanding constraint graph cycles

Hi, Since upgrading to a recent CMake, the FLightGear build system is now reporting this: == CMake Warning at utils/fgai/CMakeLists.txt:1 (add_executable): Cannot generate a safe runtime search path for target fgai because there is a cycle in the constraint graph: dir 0

Re: [CMake] Debugging custom commands with VS project generator

> On 22 Jun 2017, at 11:52, David Cole wrote: > > When you convert that error code to hex, it's 0xc139, and if you > google that, you see it's an "entry point not found" error code. > > Is something in the custom command trying to load a DLL that doesn't > have the

[CMake] Debugging custom commands with VS project generator

Hi, We’re trying to debug a failure of a custom build command, in a Cmake project using Visual Studio 2015. Unfortunately the command works on some Windows setups but not others - clearly there is something install-dependent going on. (It works on my local machine, but not on our Jenkins build

Re: [CMake] 'No known features for CXX compiler' warning with custom Clang

> On 19 Dec 2016, at 09:51, James Turner <james.tur...@kdab.com> wrote: > > In my case there is no feature_tests.cxx generated at all. For the benefit of posterity, Robert very kindly figured this out: the problem is I did not have CMP0025 set, and the minimum CMake versio

Re: [CMake] 'No known features for CXX compiler' warning with custom Clang

at to determine why feature detection is failing, since > currently it believes that none of the features listed in it are > valid. > > Now if the file is empty, that means we are looking at a CMake logic > bug somewhere before this. In my case there is no feature_tests.cxx generat

Re: [CMake] 'No known features for CXX compiler' warning with custom Clang

CXX_STANDARD_COMPUTED_DEFAULT "98") set(CMAKE_CXX_COMPILE_FEATURES "") set(CMAKE_CXX98_COMPILE_FEATURES "") set(CMAKE_CXX11_COMPILE_FEATURES "") set(CMAKE_CXX14_COMPILE_FEATURES "") set(CMAKE_CXX_PLATFORM_ID "Darwin") set(CMAKE_CXX_SIMULATE_ID "&quo

[CMake] 'No known features for CXX compiler' warning with custom Clang

there is some compiler-id detection which needs to be extended / over-ridden for my different build of Clang. Kind regards, James -- James Turner - Senior Software Developer KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: S/MIME cryptographic signature -- Powered by www.kitware.com

[CMake] Custom clang compiler unrecognised on OS-X

ppreciated! Kind regards, James -- James Turner - Senior Software Developer KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: S/MIME cryptographic signature -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FA

Re: [CMake] CMAKE_OSX_DEPLOYMENT_TARGET vs CMAKE_OSX_SYSROOT

> On 25 Sep 2016, at 16:53, Braden McDaniel wrote: > > Yes, that squares with my understanding of the current semantics. > > Interestingly, in Xcode 8, the versioned SDK directory is actually a > symlink to the unversioned one. It would not surprise me if the > versioned

Re: [CMake] CMAKE_OSX_DEPLOYMENT_TARGET vs CMAKE_OSX_SYSROOT

> On 20 Sep 2016, at 16:00, Braden McDaniel wrote: > > When setting CMAKE_OSX_SYSROOT to the unversioned directory name (using Xcode > 8, as it happens) and setting CMAKE_OSX_DEPLOYMENT_TARGET, I get this error: > > > -- The CXX compiler identification is AppleClang

Re: [CMake] Build-system dependency (as opposed to target)

> On 9 Jun 2016, at 09:51, Petr Kmoch wrote: > > I believe you're looking for the directory property CMAKE_CONFIGURE_DEPENDS ( > https://cmake.org/cmake/help/latest/prop_dir/CMAKE_CONFIGURE_DEPENDS.html ). > Adding a file path to that property causes any changes to that

[CMake] Build-system dependency (as opposed to target)

Hi, Is there a way to make the entire build-system depend on a file? I have some data I’m reading into my CMakeList.txt via file(READ), and I want changes to that file to effectively act as if the CMakeList.txt itself was modified. The read values are used to populate some variables via string

Re: [CMake] Adding entries to the info.plist file for OS X .app bundles.

On 20 Mar 2015, at 08:58, Michael Jackson mike.jack...@bluequartz.net wrote: to support Retina displays for our app. Should I just create my own template .plist file and use configure_file to add items into the file? You can do something like: # in our local CMakeModules dir add

[CMake] Correct way to set machos-min-version in Cmake 3.2.1

Hello, I’d imagine this is a FAQ, but I’ve Googled without success. Apologies if the answer is out there. With Cmake 3.2.1, some behaviour seems to have changed, in the handling of CMAKE_OSX_DEPLOYMENT_TARGET. I am trying to build using the 10.9 SDK, but with macosx-min-version set to 10.7

Re: [CMake] CMake and Framework/CFBundle Support

On 11 Feb 2014, at 07:09, NoRulez noru...@me.com wrote: Most of the things I have already implemented as post-build commands but are there also CMake ways of doing such things? .) Adding resources to CFBundles? (Resources for frameworks are supported) That would be a nice addition -

[CMake] OS-X app bundle - executable name vs bundle name

Hi, I’m experimenting with using Cmake’s bundle support on OS-X for a project. (Up until now I have assembled the bundle by hand using a separate script which also creates the DMG). I have the situation, that I need the executable name to be different to the bundle name.

Re: [CMake] ExternalProject_Add ALWAYS, VisualStudo

On 1 Dec 2013, at 10:53, James Turner james.tur...@kdab.com wrote: I am trying to force the BUILD step of an ExternalProject_Add target to be run - always. I have found several wiki articles, and references in the archives of this list, to setting an ALWAYS option for the stage I want

[CMake] ExternalProject_Add ALWAYS

: ExternalProject_Add(Foo PREFIX ${CMAKE_BINARY_DIR} DOWNLOAD_COMMAND # no need to download BUILD_ALWAYS # but is this correct? SOURCE_DIR ${CMAKE_CURRENT_LIST_DIR}/path/to/foo …... ) Kind regards, James Turner -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [CMake] CMake'ified Boost

, 2013 at 12:39 PM, Bill Hoffman bill.hoff...@kitware.com wrote: On 2/21/2013 10:34 AM, James Turner wrote: I've just setup a SuperBuild using ExternalProject, and am pleasantly surprised how well it works so far. I've encountered one issue, which is awkward - I'm basically using

[CMake] SuperProject vs SubProject generators

Hi, I've just setup a SuperBuild using ExternalProject, and am pleasantly surprised how well it works so far. I've encountered one issue, which is awkward - I'm basically using the SuperBuild to automate assembling / updating dependencies for the final sub-project, which is the real project

[CMake] Fwd: source_group(), Xcode projects

[Cmake 2.8,9, Xcode 4.4] Based on comments here, the Wiki, the manual, and many other places, I have the impression that source_group() should 'just work' with Xcode. But my experience is that no matter what I do, CMake acts as if I didn't write the source_group command at all - everything

[CMake] Xcode generation, transformation of framework includes to -F

I've encountered a problem with OSX framework detection, I think exposed due to updating to Xcode 4.3.3 (was previously using 4.3.2), though I'm sure the real issue is actually in my cmake-files. It appears that /Library/Frameworks is no longer searched by default (this makes sense for better