Enable bitcode on iOS project with static library without bitcode enabled

Is it possible to enable bitcode for a project when an individual static library isn't bitcode enabled

In our app we are using a static library which isn't bitcode enabled and in an ideal world we would have bitcode enabled for our project. The company that provides us with the static library is unable to give us a bitcode enabled version which is slightly worrying in itself, but not something I can work around at the moment.

I've been looking at ways to incorporate this library into our project through a dynamic framework, with the hope that we can then enable bitcode for this. However I haven't been able to have any luck so far.

Before I track any further into a dark hole I want to be sure what I'm looking to do is possible and if so, any advice on what would be the best way to go about it?

No it is not. If one library does not have bitcode available, then the target that includes it must also have bitcode enabled.

If you think about it, it is about what Apple compiles and delivers - this is at the level of the target or app. They need to have bitcode available for all parts of that target/app in order to compile the bitcode for the target architecture.

You have pretty much hit the hard rule in all of this.

The converse is not true. You can include libraries which include bitcode into your non-bitcode app/target. Presumably the LLVM compiler will compile the bitcode into your valid architectures, unless it finds existing slices to link against.
Enable bitcode on iOS project with static library without bitcode enabled
 
 
Q