der_path;@loader_path
> /../lib"
> )
>
> This should work, but I think CMake could use some facilities to handle
> the executables runpath search path on os x and the DT_RPATH / DT_RUNPATH
> in linux.
> best regards,
> Andreas
>
> Am 20.02.2013 um 11:39 schrieb Darrel
I think I've just answered my own question. It looks like it has to be in
the root CMakeLists.txt. If I put it in one included from
add_subdirectory() it doesn't work but in the root CMakeLists.txt it does.
On 20 February 2013 10:39, Darrell Blake wrote:
> Hmm. I've just
3 00:17, Alexey Petruchik wrote:
> Hi, I'm doing this by adding:
> set(CMAKE_XCODE_ATTRIBUTE_LD_RUNPATH_SEARCH_PATHS
> "@executable_path/../Frameworks")
> to my CMakeLists.txt. Not sure that this is the way it should be done but
> at least it works ;)
>
> Regards
Is there any way to set the XCode "Runtime Search Path" linker setting?
I've got a framework that was built using @rpath so I'm having to set the
Runtime Search Path setting to @executable_path/../Frameworks so it can be
found. I just wondered if there was any way to set it from CMake.
Darrell
--
*without CMake (not "without XCode").
Apparently I'm incapable of using email today.
On 23 November 2012 21:58, Darrell Blake wrote:
> Sorry. I sent the previous version prematurely :/
>
> What effectively happens is, in XCode I get a project that looks
oject without XCode I would just drag the resources
into the Resource group.
Darrell
On 23 November 2012 21:26, David Cole wrote:
> What do you mean they get duplicated into the Source tree? The input
> is in the source tree, right?
>
>
> On Fri, Nov 23, 2012 at 3:49 PM, Da
resource2
resource3
/Resources
resource1
On 23 November 2012 21:26, David Cole wrote:
> What do you mean they get duplicated into the Source tree? The input
> is in the source tree, right?
>
>
> On Fri, Nov 23, 2012 at 3:49 PM, Darrell Blake
> wrote:
> > I've
I've created a CMake project which adds resources to XCode similar to this:
set(source_files main.cpp file.cpp blah.cpp)
set(resource_files resource1 resource2 resource3)
set_source_files_properties(${resource_files} PROPERTIES
MACOSX_PACKAGE_LOCATION Resources)
add_executable(MyApp MACOSX_BUNDLE
Currently, I'm adding files to my XCode resources similar to this:
file(GLOB_RECURSE resFiles
${CMAKE_SOURCE_DIR}/Res/Images/*
${CMAKE_SOURCE_DIR}/Res/Music/*
)
set_source_files_properties(
${resFiles}
PROPERTIES
MACOSX_PACKAGE_LOCATION Resources
)
add_executable(Project, MACOSX_BUNDLE
I'm porting a game of mine from Windows to Mac using CMake and I've run into
a little snag.
When CMake generates the XCode project files it generates two new files for
my target (CMakeCXXCompilerId.cpp and CMakeCCompiler.c). Both of these files
contain an entry point definition which is causing XC
10 matches
Mail list logo
