Setting public headers for Xcode framework target

[novocodev]

I have built the 02-library example for Xcode with the following command:

build.py --clear --toolchain xcode --framework

This built a Framework, but it does not have any public headers in the framework Headers folder.

I added a public.h file to the example and added the following entry in the CMakeLists.txt

set_target_properties(
        foo PROPERTIES
        PUBLIC_HEADER public.h)

When building the public.h file is copied to '_install/xcode/lib/'

But the build fails with the error:

Expected only one lib in directory: .../_install/xcode/lib
But found: ['.../_install/xcode/lib/libfood.a', '.../_install/xcode/lib/public.h']

What is the correct way to configure the public headers for a framework build.

[ruslo]

Try to install headers to include directory. Explanation: this is workaround script which expect only one file in lib folder (which should be the *.a library) so when there are some other files script can't decide what file is a library.

Just for your information there are few fixes in latest CMake version that allow creating frameworks without hacks/workarounds (just using CMake). I haven't tried it yet, but if it works okay --framework option will be removed.

[novocodev]

Still using make 3.3

cmake_minimum_required(VERSION 3.3)

I added the FRAMEWORK property

set_target_properties(
        foo PROPERTIES
        FRAMEWORK TRUE
        PUBLIC_HEADER public.h)

Then I built using the following command

./buildtools/polly/bin/build.py --clear --toolchain xcode

This created a Framework with 'public.h' in the Headers folder located at:

_builds/xcode/Debug/foo.framework

But this only appears to be a MAC OS X framework not a fat Framework, I ran the file command:

file _builds/xcode/Debug/foo.framework/foo

result was:

Mach-O 64-bit dynamically linked shared library x86_64

I also tried --toolchain ios-9-2 but the framework still appears to be created only for x86_64

[ruslo]

But this only appears to be a MAC OS X framework not a fat Framework

This is by design. Fat library created only for iOS.

I also tried --toolchain ios-9-2 but the framework still appears to be created only for x86_64

I will test latest CMake version with few improvements, may be will create an example.

[ruslo]

What is the correct way to configure the public headers for a framework build

Okay, I think I know what is the problem here. --framework option expect headers be located in directory <install-prefix>/include/<frameworkname>. I.e. if you have library libfoo.dylib installed, then headers should be located in <install-prefix>/include/foo and will be moved to foo.framework/Headers. The reason of this is that project which uses foo should do #include <foo/*.hpp> in both variants. I've added warning to build.py script, so you should see next message:

Warning: no headers found for framework (dir: /.../_install/ios-9-1-armv7/include/boo)

Which can be fixed by next CMake code:

install(FILES boo.hpp DESTINATION include/boo)

I also tried --toolchain ios-9-2 but the framework still appears to be created only for x86_64

Are you sure you're using patched CMake version?

• https://github.com/ruslo/polly/wiki/Toolchain-list#ios
• https://github.com/ruslo/hunter#notes-about-version-of-cmake

[ruslo]

Example with framework and native Xcode project updated:

• https://github.com/forexample/ios-dynamic-framework#headers

[novocodev]

Great! I have successfully built and linked the ios-dynamic-framework project.

I did have to use patched CMake version, I tried with the latest 3.5.0-rc2 CMake but that failed to build the Fat framework bundle.

I'm going to try and replicate the project setup to my own library repo.

[ruslo]

but that failed to build the Fat framework bundle

With CMake 3.5+ you have to use CMAKE_IOS_INSTALL_COMBINED=YES and CMAKE_XCODE_ATTRIBUTE_ONLY_ACTIVE_ARCH=NO and run install (no need to use --framework, now it's --install). However dynamic framework will not be signed properly so the last time I've tried it I failed to run bundle on real device.

[novocodev]

I have replicated the demo project setup on my own repo, I did not copy over the custom jenkins.py as I am just trying to build a dynamic library component, I am calling build.py directly with:

./buildtools/polly/bin/build.py --clear --toolchain ios-9-2 --framework --config Release

The build is successful and the lib binary now reports as a Fat lib and the public header is copied over to the framework/Headers folder.

I have noticed that if I build with --config Debug, that 'd' gets appended to the project name for all folders and files and it also causes the public header not to get copied to framework/Headers (unless I install it to an include/'d' folder.

Is there a way to prevent the 'd' suffix getting added and maybe create the framework under a debug or release folder depending on the --config value.

[ruslo]

Is there a way to prevent the 'd' suffix getting added

Set it in command line -DCMAKE_DEBUG_POSTFIX="", in terms of build.py script it will be --fwd CMAKE_DEBUG_POSTFIX=""

[novocodev]

Both iOS and OSX framework builds are working, thanks.