Setting up my M1 mac for Universal binary compiles....

d.healey

@Lindon Not as far as I know

Lindon

@d-healey ok great, thanks again - now just to sit on my hands and wait for it to get shipped.....oh except to ask -- where do I get XCode 13.1 from?

d.healey

@Lindon If you have an Apple developer account there is a page you can download all the old versions. I can't remember the link so you'll need to Google

orange

@Lindon You can download old versions from here: https://developer.apple.com/download/all/

You need to login to your Apple Developer account to see that page.

thet

Hi! I'm just trying out HISE for the first time (on an M1 Mac)

Is the info on this thread still correct for HISE 3.0.1?

I have Xcode 13.2 Do I still need to downgrade to 13.1?

thanks!

I also saw on another thread that there is no need for ipp on mac, is that right?

Christoph Hart

Nope the latest Xcode version works too. And yes you can disable IPP on macOS

thet

@Christoph-Hart thanks - yes it seems to compile and run, though as a debug version, but thats just my ignorance of Xcode I think.

I tried to export an au plugin using the tutorial examples, but it finished suspiciously quickly and I don't think it did it. can't find any output anyway.

d.healey

@thet Build for profiling is what you want. The AU (.component) will have been placed in the correct folder on your system so that when you open you DAW it should be there waiting for you.

thet

@d-healey thanks. Yes build for profiling works, looks like archive will also work.

There's a bunch of errors in terminal when I try to export the AUi

HISE/HISE-3.0.1/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: No such file or directory

turns out the folder is actually called projucer - renamed it to Projucer and got a bit further.

now I have this error:

Compiling Instrument plugin BasicSynth ...
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

thet

@thet I tried exporting as a vst as well, it just says VST SDK is missing no matter what I do, I worked through a long thread from several years ago and tried all the things it said, but never got past that error.

the zip file of the sdk is there, I tried that, and copying the sdk out of the JUCE location, and deleteing cahes and so on..

I think there may be naming and path problems in the default setup.

could it be that I'm on a macos case sensitive drive? is naming in hise assumed to not be case sensitive?

is there anyone on an M1 mac that is successfully exporting to vst?

vst3 will do I don't care about vst2.

I have tried with and without the vst3 enable box ticked in settings.

d.healey

@thet Perhaps you missed the step of extracting the VST SDK?

https://youtu.be/zeLeCSNh0XM?t=146

thet

@d-healey I had extracted the sdk from the zip file but I had left it in the directory created byy the unzipping so it was at : /HISE-3.0.1/tools/SDK/sdk/VST3 SDK

i moved it to: /HISE-3.0.1/tools/SDK/VST3 SDK

and that fixed that error

now however I have the same error that I had when trying to export as AU

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

d.healey

@thet That one has been covered before, I think a search of the forum or Google will reveal an answer. I can't remember what the solution was.

thet

@d-healey right fixed that with this:

xcode-select — install
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -license accept

now it starts compiling but complains about lack of ipp - i will check that - thought I'd told it not to use ipp.

d.healey

@thet Did you disable IPP in your project's preferences?

andioak

@Lindon said in Setting up my M1 mac for Universal binary compiles....:

What OS do I need to be running? - I'm guessing its coming with V12(Monterey)

Traditionally the OS that your new mac comes with is the lowest macOS version that you can run, sadly. So if there is a need for backwards compatibility (when is there not?) that may present issues. Virtualization for pure testing can of course be done in VMWare Fusion including sound and drivers actually, but building/compiling via virtualized macOS is ill advised, I tried :(

What version of Xcode do I need (bearing in mind that there's at least one of the later versions that wont work with HISE)

Xcode can most likely be run in a few lower versions than the latest, even though the OS is newer and not explicitly supported. Reference the Xcode versions easily here:

https://xcodereleases.com/

Nice overview there. But do download from your account from the link that @orange left above.

Setting up my M1 mac for Universal binary compiles....

17

1.8k

10.4k

90.8k