XCode Linker error on latest Mac static lib (Invalid bitcode version)Answered

Hi,

I am trying to build with the latest static lib available on the site (4.4.4.0) but get the following linkage error on x86_64:

'Invalid bitcode version (Producer: '1205.0.22.9.0_0' Reader: '1200.0.32.29_0')'

Is it because of the XCode version? If so, could you please post one that works with 12.4? And a Universal one?

If I want to install the latest XCode 12.5 update I need to also upgrade my system from Catalina to OS X 11 (damn Apple!) and I'm in the middle of important projects so I'd rather avoid.

Thanks.

Mariano

Answer

Static libraries require the latest public XCode.

Dynamic libraries are more flexible.

I build plugins, so I prefer not to have to worry about a separate dylib. Where would I have to store it i this case?

There are a thousand ways to skin that cat. It depends on the apps loading the plugins and the particular quirks of those apps.

Well, that's where it becomes complicated. There are hundreds of possible DAWs loading these plugins

> Static libraries require the latest public XCode.

Is it a technical issue or is it feasible to build a static lib for XCode 12.4? It's only the previous XCode version

It's not technically feasible to support more than 1 version of compiler that impose arbitrary restrictions on their static binaries.

This is a solvable problem. Microsoft solved it decades ago. Now Apple engineers have to put in the hard work to solve it. (Will they? Likely not.).

So, if you want to use the static libraries use the latest XCode.

Ok, so my options are:

a) upgrade my main system from Catalina to Big Sur and risk my current projects to be messed up and delayed because of it

b) use another machine on Big Sur, moving all source files, libraries, certificates etc… to build an update with the static lib

c) build the update with dylib, but then going through the process of finding out where the dylib needs to be stored for plugins

d) refund my 2 clients who face activation problems

None of these options is very appealing to be frank. I would expect you to keep a static lib available for at least the previous version of XCode. 

Option C is the best solution moving forward so you're not chained to specific XCode versions. Also, the dynamic libraries are *always* the better choice.

Reply
Discard post