Re: [CMake] Cmake Frameworks and Bitcode

2018-03-26 Thread Brad King
On 03/26/2018 04:24 AM, Cameron Palmer wrote: > However, setting the property BUILD_WITH_INSTALL_RPATH on or off doesn't > change anything as far as I can tell. The target is still linked with > -headerpad_max_install_names and the linker still complains. Oops, I mixed up functionality with other

Re: [CMake] Cmake Frameworks and Bitcode

2018-03-26 Thread Cameron Palmer
Quite possible I’m misunderstanding something, but… As you said, I really don’t care much at this point about the RPATH. However, setting the property BUILD_WITH_INSTALL_RPATH on or off doesn’t change anything as far as I can tell. The target is still linked with -headerpad_max_install_names an

Re: [CMake] Cmake Frameworks and Bitcode

2018-03-19 Thread Brad King
On 03/12/2018 10:36 AM, Cameron Palmer wrote: > So after a bit of hacking it seems that Cmake should provide something like: > > CMAKE_OSX_BITCODE_ENABLE For reference, this refers to a previous post: Bitcode and CMake https://cmake.org/pipermail/cmake/2018-March/067191.html with the go

[CMake] Cmake Frameworks and Bitcode

2018-03-12 Thread Cameron Palmer
So after a bit of hacking it seems that Cmake should provide something like: CMAKE_OSX_BITCODE_ENABLE Which would pass -fembed-bitcode to the compiler and linker and remove the option in Darwin.cmake for -Wl,-headerpad_max_install_names in CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS. Does this sound l