Mac OS build problems
-
One thing I also confused about: Do I need to have JUCE installed also? Because at some point when I launched Projucer it said that there was a newer version available and it prompted me to download it. But now if I search my HD for Projucer there are like 4 different installs of it on my machine now... one with the JUCE install, one in the HISE source folder and a few other locations.
Also, I just downloaded the updated HISE 3.6 and now it won't even launch ... it just bounces up and down on my dock and not responding. I even restarted my iMac to see if that had anything to do with it....
-
This is my machine specs:
-
@ElectroBlue said in Mac OS build problems:
Do I need to have JUCE installed also
Everything you need (other than xcode and xcpretty) is included in the HISE source download. This includes a modified version of JUCE and the Projucer application.
But now if I search my HD for Projucer there are like 4 different installs of it on my machine now
Remove every copy of the HISE source code you have and start again.
Because at some point when I launched Projucer it said that there was a newer version available
Ignore that, click the button to disable it from popping up again.
-
@d-healey Ok, I deleted my JUCE download and JUCE install and removed and deleted all HISE source code as well as the HISE app in my Applications folder and started over.
I then went to the HISE website and downloaded the HISE 3.6 pkg file and the HISE 3.6 source code ZIP file. I installed the HISE 3.6 pkg file so the HISE app is now once again in my Applications folder. I unzipped the HISE 3.6 source code and created a new folder called "HISE Source" and moved the source code folder "HISE-3.6.0" into this new folder.
I then launched the HISE applications and it won't launch. It just bounces up and down and not responding.
-
@ElectroBlue Sounds like a permission issue. I'm assuming the pkg isn't signed.
Anyway forget about the prebuilt pkg. Your goal is to compile HISE, right? So just focus on doing that.
-
@d-healey Haha no, my goal was to export my HISE project to a Mac standalone app and AU and VST plugin formats. But if I have to actually compile HISE itself first before I do that then I'll do it ... if I can figure out how... remember I'm a beginner at this. lol
-
@ElectroBlue said in Mac OS build problems:
Haha no, my goal was to export my HISE project to a Mac standalone app and AU and VST plugin formats.
That's the same thing ;) Building HISE and building your plugin is the same process.
@ElectroBlue said in Mac OS build problems:
if I can figure out how... remember I'm a beginner at this. lol
I have videos on YouTube about this. Have you seen those?
-
@d-healey Also, I was going through the HISE docs and I downloaded the VST SDK from Steinberg's website. I wasn't sure about the Intel IPP because I'm on a Mac, but I'm on an Intel Mac so I guessed that maybe I need that too? But when I clicked on the link the page that opened said that that page was missing so there is a broken link in the documentation...
So I searched on the Intel website and found this: [link text] Intel
Integrated Performance Primitives for Intel oneAPI Base Toolkit(https://www.intel.com/content/www/us/en/docs/ipp/get-started-guide-oneapi-macos/2022-2/overview.html)
and I installed it. Is that all I need to do for that part? -
@ElectroBlue said in Mac OS build problems:
was going through the HISE docs and I downloaded the VST SDK from Steinberg's website. I wasn't sure about the Intel IPP because I'm on a Mac, but I'm on an Intel Mac so I guessed that maybe I need that too?
Everything you need is included with the HISE source. You don't need to use IPP on Mac (in fact you don't need to use it on any OS, it's optional on Windows and Linux).
-
@d-healey Ahhhh ok! I think I'm beginning to understand how this works now. Ok, I do remember seeing your YouTube video about how to build HISE... I just skipped it because I had just downloaded what was on the HISE website and already started using it to build my instrument. But I'm beginning to see the importance of it now! lol My goal now is to master doing that first before I do anything else.
-
@ElectroBlue said in Mac OS build problems:
My goal now is to master doing that first before I do anything else.
A very wise idea. Once you get over this bump it will be plain sailing - well actually you'll need to get over the same bump on Windows too, but then it will be plain sailing, mostly :)
-
@d-healey Ah Ok Got it! Thanks for clarifying that. :)
-
@d-healey Ok, good to know. You are the expert at this so I will follow your lead. :)
-
@d-healey Ok, so I watched your latest video on Patreon/YouTube and followed all your instructions for Mac OS: I installed xcpretty and GIT. Xcode 15 Beta 6 with command line tools I had already installed. It took a while but it finally finished and it said it completed successfully...
It created a HISE folder with everything inside but when I launch the HISE app from ...
I'm having the same issue as before: The app never launches ... it bounces up and down for a bit and then not responding...
So... hmmmm .... what could be going on here? I did see quite a bit of yellow warnings as I was running your script in the Terminal but I didn't see any error messages. Maybe I need to restart my iMac again?
-
@ElectroBlue Open HISE in the terminal (drag the app onto the terminal window and hit enter) and see if you get any errors.
-
@d-healey It says "permission denied"
-
@ElectroBlue Try the
chmod +xcommand. -
@d-healey said in Mac OS build problems:
chmod +x
I tried that. It doesn't fix the problem. My computer hates me! lol
I don't remember what command to use after SUDO if I was going to try that. -
@ElectroBlue Why is your user called test?
You might need to open gatekeeper, or whatever security settings your version of MacOS has and whitelist the HISE application
https://support.apple.com/en-gb/guide/mac-help/mh40616/13.0/mac/13.0
-
@d-healey said in Mac OS build problems:
Why is your user called test?
I don't know? It's been that way for years. I think a long time ago I was having some issues so I created a new user account called "test" to see if the problem still existed in a fresh user account ... and it didn't so then I just used that account.
