If you want the INSTALL_NAME_DIR to have effect in the build tree, you also need
set_target_properties(EMsoftLib PROPERTIES BUILD_WITH_INSTALL_RPATH ON)
Clint
- On Dec 5, 2016, at 8:22 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
> I have this:
>
> if(APPLE AND BUILD_SHARED_LIBS)
I have this:
if(APPLE AND BUILD_SHARED_LIBS)
set_target_properties(EMsoftLib PROPERTIES MACOSX_RPATH FALSE)
set_target_properties(EMsoftLib PROPERTIES INSTALL_NAME_DIR
"${CMAKE_LIBRARY_OUTPUT_DIRECTORY}")
endif()
--
Michael A. Jackson 400 S. Pioneer Blvd
Owner, President
Do you want the library identification to be a full path?
set_target_properties(foo PROPERTIES MACOSX_RPATH OFF)
Clint
- On Dec 5, 2016, at 7:38 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
> what combinations of RPATH variables do I need to set to get a full,
> absolute path to
what combinations of RPATH variables do I need to set to get a full,
absolute path to a build library in my build tree? THis is on macOS
10.10.5 and cmake 3.5 and above. I have tried all sorts of combinations
and I either get just the library name or @rpath/library.dylib neither
of which is goi
I'm having an issue building a child project through my master project
where the child project is an "External Project" which is automatically
built using CMake's "ExternalProject_Add" feature if it is not found (using
"FindChildProject.cmake"). The error message happens during installing of
the ch
>
> The library linking against "originalLibraryForward" has to be
> compiled from the original sources too. Actually performing the
linking step should be sufficient. Is there a way to accomplish that?
>
Object libraries are what you need here. See
https://cmake.org/cmake/help/v3.7/manual/cmake
I am using the BundleUtilites on macOS to create a redistributable
package that consists of a large number of command line programs,
libraries and other assorted support files. The issue that I am having
is that each time BundleUtilities runs on a given executable, it will
also attempt to "fix
On 12/03/2016 06:52 AM, Dan Liew wrote:
> There was a post about this 10 years ago [1], has anything changed since then?
No. From my response back then:
>> The "clean" target is not a first class target available to
>> CMakeLists.txt codeWe do plan to make targets like install
>> and clean f
Hi,
I am trying to put
set(CMAKE_EXPORT_COMPILE_COMMANDS ,1) inside a toolchain file but the
command has no effect there. I've tried to put it in CMakeLists.txt too
using the previosly set and
add_definitions(-DCMAKE_EXPORT_COMPILE_COMMANDS=1) without success.
The command only works in command li