OS Deployment Target set to 10.7.
I use C++14.
OSX Architecture: 64 bit.
Base SDK: 10.11
I’ve also -Ofast instead of the default O3 optimisation.
Still, some 10.7 and 10.8 users are reporting that the plug-in is not appearing in their DAWs.
I’ve made sure that they use a 64 bit DAW, but still the plug-in is not there.
Is there some compatibility check list for supporting 10.7?
If your using C++14 library features (not just syntax), I don’t think that would work on those OS’s due to their age. A dynamic library is shipped with the OS.
TL;DR: the order in which AudioUnit.framework and AudioToolbox.framework are linked matters, they must be linked in that order, at the end of the mentioned topic it’s explained how to make sure they are
I see in that thread that t0m says that it’s a specific issue with SDK 10.15, but I’m using 10.11 (I’m using that one because I saw in another thread that in order to support 10.7 you have to use that SDK).
But anyway, I just checked and AudioUnit.framework is linked before AudioToolbox.framework.
Do you have access to a 10.7 machine? In my opinion the best next step would be to get the system logs from console.app during the attempted load. That might tell you what C++14 function is failing to load or just give you more information about the issue in general. You could also try loading your plugin in a debug build of the juce plugin host and see how things fail.
Yes, but if a binary fails to load (which is very likely the cause why it is not recognized) you end up with a few messages in the system log inside console.app.