[CMake] Rolling up Object libraries into a final product

I’m using object libraries to put together a project composed of numerous modules. When putting together the static library (deliverable) at the end I have used libtool to assemble final product. I’ve been trying to adopt the use of OBJECT type libraries to avoid the libtool call and it mostly w

Re: [CMake] Cmake Frameworks and Bitcode

ote: > > 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.

[CMake] Cmake Frameworks and Bitcode

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

[CMake] Bitcode and CMake

I’m building frameworks for iOS/tvOS with bitcode at the command-line. In order to compile and link I need to add two things: target_compile_options( library PUBLIC -fembed-bitcode ) target_link_libraries( library PUBLIC -fembed-bitcode ) This works, but yields the complaint that: ld: warning:

Re: [CMake] add_custom_target

be insignificant. I'd also point out that the build time increase > is somewhat balanced out by not fetching tens of thousands files from source > control... > > This may help shape your thinking? > > Mark > > -Original Message- > From: CMake [mailto:c

[CMake] add_custom_target

I’m using ExternalProject_Add to download a Git project that is a pre-requisite of my project. For the sake of the discussion I’ve wrapped OpenSSL and Boost in this manner placing tagged version of the source in my repo. Building them isn’t really a problem, they run, take a long time compiling.