Develop branch build status
-
@dustbro True! Maybe I'll try 12.2 quickly... ALthough quickly doesn't exist when it comes to downloading and unpacking XCode!!!
-
@UrsBollhalder Let me know how you get on, I need to do some compiling on MacOS soon.
-
@d-healey Well, so far no luck... 12.2 didn't resolve the issue... I'll keep you posted.
-
Success with Xcode 13 - will probably work with 12x too.
I just had to disable un-needed architectures.
-
@d-healey said in Develop branch build status:
Success with Xcode 13 - will probably work with 12x too.
I just had to disable un-needed architectures.
I'll try that right now... I've been at it for 2 days now... losing my shit... unable to get a working compile on Big Sur!
I get a bunch of these now... I believe to know that these are vst sdk-related but I don't know where to fix it! I think the sdk-path is not set correctly... but where!??!!
-
Nothing to do with the SDK, that only comes into play when exporting plugins. This error is because Christoph removed the STK nodes from script node but you still have the modules in your .jucer file. You need to remove it or use the .jucer file from github.
-
@d-healey Ok... I just removed that module... But I still get a shitload of those Reference to 'Point' is ambiguous - errors... Any ideas? I'm on XCode 13 now...
I have:
- deployment target set to 10.14
- disabled all unwanted architectures
- IPP installed and path-fixed on my HD
- also tried with the deprecated legacy build system
BUT... I somehow was trying to compile the master branch... Very mysterious... trying again now...
-
@UrsBollhalder said in Develop branch build status:
I somehow was trying to compile the master branch.
How many copies of the HISE source code do you have on your system? ;)
-
@d-healey ONE!!! I set up a clone and pull directly from Christoph's repo! As you instructed me master Jedi!
But I have a working backup on an external drive though... but just for emergencies.
And also...
-
@UrsBollhalder So in hindsight... Big Sur, XCode 13, new_layout branch
-
XCode 13 and Command Line Tools for XCode 13 installed (https://developer.apple.com)
-
deployment target set to 10.14 (you can and probably should do this in multiple places => projucer and XCode)
-
disable all unwanted architectures (as posted by @d-healey above)
-
IPP installed and path-fixed on my HD (@LinuxVst has a great post about this, more or less up on top in this thread)
-
I ran into problems a couple of times when XCode doesn't have full disk access => macOS system preferences
-
-
@d-healey Have you tried to compile a plugin yet?
-
@UrsBollhalder Yes, worked fine, VST3 on all three operating systems and AU on Mac.
-
@d-healey Hmm... Directly from HISE or did you have to tinker the Xcode file before? I only could export a debug version from Xcode, but not a release! Also, what is the process for vst3 export?
-
@UrsBollhalder said in Develop branch build status:
Directly from HISE
Yes, I might have tweaked something in the .jucer file, can't remember, but didn't change anything in xcode.
what is the process for vst3 export?
Check the vst3 box in project preference before export.
-
@d-healey said in Develop branch build status:
Check the vst3 box in project preference before export.
Do I need a special sdk in the HISE folder for that?
-
@UrsBollhalder It's included with JUCE so you don't need to do anything.
-
@d-healey I get these:
Any idea what the problem could be? Why is it building for arm-64?
-
@UrsBollhalder Looks to be IPP related, I don't have IPP installed. Try exporting with IPP disabled.
-
@d-healey It was disabled actually when this happended... Now I checked IPP again, but same result...
-
@UrsBollhalder said in Develop branch build status:
It was disabled actually when this happended...
Open the .jucer file and see if there is anything suspicious there
