HISE Build Fail (Scriptnode 22nd Oct Standalone) (SOLVED)
-
@d-healey Cheers dude. I just tried all of those now but still no luck. Same errors and failed build :(
@Christoph-Hart That's a bit strange. I've downloaded it 3 times now and given it a new folder each time so it shouldn't be reading anything from anywhere else? It always says 146
-
@SteveRiggs Record the whole process outlined by Lindon and post it so we can look for any problems.
-
@d-healey Ok. Just uploading now....
-
-
Do you have this in the extra linker flags?
/opt/intel/ipp/lib/libippi.a /opt/intel/ipp/lib/libipps.a /opt/intel/ipp/lib/libippvm.a /opt/intel/ipp/lib/libippcore.a
-
@SteveRiggs There is 2 strange things in the video
- In Juce you have "OSX Architecture" on Universal Binary (32/64-bit) and that will not work 'cause OSX only accept 64 bit now
- It's strange that in Juce, the ipp settings are enabled because when you open a fresh Hise project you should open it with Projucer that are in the "Tools" folder inside the same Hise project that you are opening, and the default settings for ipp is "disabled".
So make sure to open the fresh Hise source code with with Projucer from inside the same source code.
-
@ulrik I've tried it on both 64 bit and 32/64 bit dude but get the same failed build and errors. I'm on Xcode 8 and Mac OSX High Sierra so 32/64 bit should still work. It has every other time I've built previous versions.
It's definitely the new projucer file I'm opening as well. I've opened it both from double-clicking on the 'HISE Standalone.jucer' file inside the 'projects/standalone/builds' folder itself, and also from opening the 'Projucer' file in tools. Same results each time.
I need the IPP setting enabled. A couple of times it has opened up as blank or disabled and I've had to change it to enabled manually. Very weird.
@d-healey I do have some IPP code in this bit below:
Should that code you just put be added too? I can't see anywhere that says 'extra linker flags' anywhere? Could it be here?..
-
This is what mine looks like, you need to check under the Xcode section, not the Release or Debug part.
The universal binary should work fine on your version of MacOS.
Ulrik is correct about the IPP, this is disabled by default in the hi_core section (I just downloaded the latest from github to check) so it's strange that it's showing as enabled in the video.
-
Also, where did you get that version of Projucer? The one that's in the scriptnode folder is 5.4.3.
-
@d-healey Ah yes, thats already in the Xcode section.
It is weird about the IPP 'enabled' part. I did have to change it to enabled myself manually a couple of times but it opens up with it already enabled every time now.
I've just checked the location in the hi-core section and it says its coming from the correct folder.
-
Try opening the jucer file in the Projucer that comes with the HISE source code.
-
@d-healey I've tried a few ways around now and still having the same errors.
There's the 'Projucer' file in tools that I've opened direct, also the Hise standalone jucer file.
First time I tried I just double clicked the 'HISE Standalone.jucer' file in the new source code (which must be projucer 5.4.3) but that didn't open anything at all originally. Just double clicked but nothing opens.
So then I tried right clicking and opening the same file with 5.2.0. Then it opened but it said I needed to update to 5.4.5.
I've tried multiple times with all 4 now and also tried changing the 32/64 bit but non seem to work :(
-
Open the Projucer from the tools folder directly. Then load in the
.jucer file
by File >> Open. (I'm opening the GNU/Linux version in the below video but the Mac version should be the same). -
@d-healey I thought we had it then!! It got all the way to the end this time and then failed but with a bunch of new errors now :(
It did load up with the IPP disabled this time though.
-
Do you have
USE_IPP=1
in the extra preprocessor definitions? -
@d-healey said in HISE Build Fail (Scriptnode 22nd Oct Standalone):
USE_IPP=1
That's the one!!! It was blank before. I just added that in and it finally worked!!! Amazing mate. Thank you.
Damn, that was much harder than it should have been
Happy days! Thanks all for your help today!! I'll remember this one for next time I build just in case!
-
@SteveRiggs I'm really glad it worked out alright! Cheers!
-
@ulrik Cheers dude :)