@Christoph-Hart Okay, I see. Too bad but I see the time-sucking black hole in re-inventing the wheel for you, especially for such a unique computing environment. Already lots of time spend making new features and fixing bugs. Not worth it.
can I build HISE with C++ 14?
if not, is there a dedicated installation of C++ 17 I can add to macOS 10.13?
what is the minimum target OS on macOS / iOS for this newest build of Develop branch?
What is the minimum version of Xcode for building HISE?
@d-healey Yeah it's weird. When I do it your way in the Projucer (so XCode does the codesign), then notarization fails and I have to replace the code signature manually...
Although for one of the projects (for which I enabled audio inputs), it is the opposite. Manual codesign (altool) works but the microphone access isn't allowed - resulting in a successfully codesigned/notarized app but the audio input doesn't work - after being hardened. While through Projucer/XCode you can specify the mic access and the codesign/notarization works, so it is strange...
I can't find the altool command that allows hardening with authorised mic access (and I don't have a machine recent enough to try with the new notarytool).
So in definitive, I don't understand why I can make the manual codesigning work when it doesn't from XCode and vice-versa for another project, despite the certificate being the same (so the team and app ID...). I don't know if all of this is related to the timestamp issue you mentioned, I will perform more tests in the next few days.
I definitely should use a VM instead of a too annoying dual boot...
I was triple booting my previous Mac Mini but the new one only has a tiny unchangable ssd (128GB!) so I decided to go for bootcamp for Windows on an external drive and a virtual machine for GNU/Linux. But I think I'm going to move Windows into a VM too because it's a hassle to reboot the Mac and hold down ALT and hope that it decides to let me switch to Windows.