HISE Build Fail (Scriptnode 22nd Oct Standalone) (SOLVED)

[d.healey]

@SteveRiggs
https://www.youtube.com/watch?v=zeLeCSNh0XM

How do you make a shorcut to HISE in MacOS?

[SteveRiggs]

@d-healey Very strange. That's the exact video I follow every time I do a new build. Same process this time.

I understand now that the folder is actually the source code.

That should work then but I'm still getting the same errors and a failed build. I've tried with both Universal Binary (32/64-bit) and also 64bit intel but get the same errors with both.

I also just tried renaming the old build folder before attempting the new build. Still no good :(

[SteveRiggs]

@d-healey To make an alias/shortcut I just right click on the HISE icon in the MacOSX/build/Release folder and go to 'make alias' and then drag and drop that onto the dock and rename it

[d.healey]

Are you sure that you are opening the new .jucer file and not the old one? By default projucer opens that last opened .jucer file.

[SteveRiggs]

@d-healey

Yeah, I went to 'new project' in projucer, then 'open existing project', and chose the 'HISE Standalone.jucer' file from the newly downloaded source code folder.

Then I go to 'Save Project and Open in IDE' and it opens Xcode.

I notice when Xcode opens though, the last failed build is still there with all of the errors.

It does say it's indexing the files and the progress bar goes along like it's reading the new file but then once it's done it still has the failed build and errors there in the top bar and side panel. Should that be happening? Surely it should refresh? When I try and build it still fails every time.

[d.healey]

@SteveRiggs I'm not sure, I don't know enough about xcode. If you've deleted/renamed the old source code folder though then I don't think xcode could still be loading it, unless it has some weird cache thingy.

Does the newly downloaded jucer file have all the correct paths and flags setup for IPP? I use git pull so I rarely have to check this myself.

[SteveRiggs]

@d-healey

It looks as if the IPP paths are right, and the path in Xcode looks like it's coming from the new source code folder.

I've also renamed the old source code folder temporarily but it's still failing

[SteveRiggs]

I also just tried deleting the new source code folder and redownloading a fresh one. Still the same errors though and failed to build.

[d.healey]

I'm out of ideas for now, could be to do with the version of xcode...

[Christoph Hart]

hmm, I remember @ulrik had the same compile errors a few weeks back but he was able to resolve it somehow. It had definitely have something to do with cached files and XCode project settings.

It definitely builds on Xcode 8.3.2 (my build server uses this old version).

[SteveRiggs]

@d-healey No probs mate. Cheers for all the help anyway.

@Christoph-Hart It is weird. The last scriptnode version from 7th Oct built perfectly first time using Xcode 8.

I wonder how I clear the cached files in Xcode then or get the settings correct. I'll have another look now...

[SteveRiggs]

@Christoph-Hart It always seems to fail when it gets to 'compiling 12 of 146 source files'... if that means anything at all?

[d.healey]

https://stackoverflow.com/questions/38016143/how-can-i-delete-derived-data-in-xcode-8
https://macpaw.com/how-to/clear-xcode-cache
https://developerinsider.co/clean-xcode-cache-quick-fix/

[Christoph Hart]

Huh? Why is it compiling 146 source files? It's only 73 source files here :)

Definitely some weird glitch...

[SteveRiggs]

@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

[d.healey]

@SteveRiggs Record the whole process outlined by Lindon and post it so we can look for any problems.

[SteveRiggs]

@d-healey Ok. Just uploading now....

[SteveRiggs]

@d-healey https://youtu.be/rtJdSmZtSZo

[d.healey]

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

[ulrik]

@SteveRiggs There is 2 strange things in the video

1. In Juce you have "OSX Architecture" on Universal Binary (32/64-bit) and that will not work 'cause OSX only accept 64 bit now
2. 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.