Re: [CMake] DEPFILE usage in add_custom_command(...)

2018-12-17 Thread Ed Branch
The target name in the depfile does not match the target name on the ninja build line due to absolute vs relative path mismatch. Even though they refer to the same file, the target names must match exactly. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

Re: [CMake] Super builds and export with Namespace

2016-08-12 Thread Ed Branch
We do it like this: - in projectA/CMakeLists.txt: set( ProjectA_IN_TREE TRUE CACHE INTERNAL "" ) - in projectA/ProjectA-config.cmake.in (which is converted to ProjectA-config.cmake by a call to configure_package_config_file from the CMakePackageConfigHelpers module): if( Projec

Re: [CMake] Create space delimited string with $ genex

2015-07-10 Thread Ed Branch
Hello, in my build process I need to call a compiler like tool with the same include directories as a certain target. I tried the following: cmake_minimum_required(VERSION 3.2) project(cmake-genex C) add_library(dummy dummy.c foo.c) target_include_directories(dummy PUBLIC foo bar) set(prop "$

[CMake] Problems on OS X with fixup_bundle

2013-02-17 Thread Ed
to each other or the systems libs which are common to all Macs. But the plugins .dylibs still have the paths for all dependencies (which are wxWidgets .dylibs) still pointing to the place were they were originally built, which was built using homebrew. My question is can I tell Cmake to fi

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

2013-02-08 Thread Ed
Sean: On Feb 8, 2013, at 11:00 AM, Sean McBride wrote: > On Fri, 8 Feb 2013 10:53:16 -0800, Ed said: > >>> I've never heard of "CMAKE_OSX_64" and google has only 7 results… >> >> "CMAKE_OSX_64" is just a variable in the cmakelists.txt fil

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

2013-02-08 Thread Ed
Sean: Thanks for the suggestions. On Feb 8, 2013, at 9:39 AM, Sean McBride wrote: > On Fri, 8 Feb 2013 09:22:12 -0800, Ed said: > >> Here is what I tried: >> cmake -DCMAKE_OSX_64=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=10.6 - >> DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

2013-02-08 Thread Ed
10.6 SDK? So many questions, and no answers on the cmake Website. Thanks, Freddie On Feb 7, 2013, at 5:18 PM, Sean McBride wrote: > On Thu, 7 Feb 2013 17:05:55 -0800, Ed said: > >> I am trying to build an app to be compatible with Mac OSX systems 10.6, >> 10.7, and 10.8 usin

[CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

2013-02-07 Thread Ed
Hello: I am trying to build an app to be compatible with Mac OSX systems 10.6, 10.7, and 10.8 using the command line with cmake. I have successfully built it for 10.7.5, now I would like to expand this app to be compatible with 10.6 and 10.8 is this possible? This is the command I am issuing to

Re: [CMake] Issue w/ relative library paths between targets in CMake 2.8 / Visual Studio 9 2008

2010-06-25 Thread Ed Loper
On 6/10/2010 2:34 PM, Ed Loper wrote: I have a CMake project that works fine with CMake 2.6, but when I build Visual Studio output with CMake 2.8, it doesn't seem to get the target library linking information quite right. [...] I managed to track down the cause of this problem. It c

[CMake] Issue w/ relative library paths between targets in CMake 2.8 / Visual Studio 9 2008

2010-06-10 Thread Ed Loper
I have a CMake project that works fine with CMake 2.6, but when I build Visual Studio output with CMake 2.8, it doesn't seem to get the target library linking information quite right. Here's a simplified version of my project: Project/CMakeLists.txt -

[CMake] xxxxxSPAMxxxxx Simple Question Regarding Link Libraries on Linux

2010-01-05 Thread ed . jung
;ll get an error about not begin able to find the library, since it's using the -l flag for the linker.  I'd rather not have to rename foo.a, because it will affect other existing software.Thanks,-Ed ___ Powered by www.kitware.com Vi