sday, February 5, 2019 at 3:37 PM
> *To: *"Stephens, J. Adam"
> *Cc: *"Maynard, Robert (External Contact)" , "
> cmake@cmake.org"
> *Subject: *Re: [CMake] [EXTERNAL] Re: Linking to boost on OS X 10.12
>
>
>
> Hello,
>
>
>
> Are you
To: "Stephens, J. Adam"
Cc: "Maynard, Robert (External Contact)" ,
"cmake@cmake.org"
Subject: Re: [CMake] [EXTERNAL] Re: Linking to boost on OS X 10.12
Hello,
Are you able to use BUILD_WITH_INSTALL_RPATH:
https://cmake.org/cmake/help/v3.13/prop_tgt/BUILD_WITH_INSTAL
Robert,
We unfortunately can't just modify the boost libraries where they are installed
because our customers need to be able to build our project from source, and
they would need to do the same thing. We could perhaps do something more
radical like copy those libraries into the build tree and
Hello,
Are you able to use BUILD_WITH_INSTALL_RPATH:
https://cmake.org/cmake/help/v3.13/prop_tgt/BUILD_WITH_INSTALL_RPATH.html
https://cmake.org/cmake/help/v3.13/prop_tgt/INSTALL_RPATH.html#prop_tgt:INSTALL_RPATH
Regards,
Juan
On Tue, Feb 5, 2019 at 4:00 PM Stephens, J. Adam via CMake
wrote:
I don't know if it is an option in your case, but you could build boost
yourself as static libraries. Then the whole build/install rpath situation
goes away. In case it is helpful, I recently gave an example of how I'm
currently doing this with a FetchContent-based solution. It won't suit
The version of the libraries that you load from your build directory
would need to be fixed up to.
On Tue, Feb 5, 2019 at 5:00 PM Stephens, J. Adam wrote:
>
> Hi Robert,
>
> Thanks for your reply. We do use install_name_tool and the like when
> installing/packaging, and our packages continue to
Hi Robert,
Thanks for your reply. We do use install_name_tool and the like when
installing/packaging, and our packages continue to work fine on OS X 10.12. My
question is about what to do with executables before packaging, while they are
still just in the build tree. We need them to work for
