Issues building HISE on Windows 11
-
@VirtualVirgin Add USE_IPP=0 to the preprocessor definitions.
-
@d-healey What should I do about the other definitions that were there and now not?
I don't know what they are. Should I add them? I don't know how they are worded. -
@VirtualVirgin It sounds like you might have multiple copies of the HISE source code? Are you using git?
-
@d-healey I'm not finding any other copy of the source code on this computer (except under "Roaming\Recent" - so just a reference to the one I was just using). I have not built on Windows yet.
-
@VirtualVirgin Let's start over.
Delete any copies you have.
Redownload the zip of the develop branch (or better, use git).
Extract it.
Extract the SDKs in the tools folder.
Launch Projucer from the tools folder.
In Projucer go to File >> Open and select the standalone juicer file from the source code you've just downloaded.
Add USE_IPP=0 to the preprocessor definitions. -
@d-healey So I tried this list (which is close to what I had done for the last three attempts).
This time I extracted the .zip directly to the the one I downloaded instead of copying that to some other place on my computer. This time it looked like the Projuicer initialized again, as it had the popups appear in the lower left to ignore.
When I checked the Preprocessor Definitions however it still said "PERFETTO=1" .
I tried adding the "USE_IPP=0" as you suggested:
But building in Visual Studio is still giving me the same errors about the ipp:Ideas?
-
@VirtualVirgin Ah ok, I see the problem. You're looking at the "Preprocessor Definitions" in the individual exporter configs (Release, Debug, etc.). You need to click on the exporter itself (Visual Studio 2022) and it's the "Extra Preprocessor Definitions" you want.
-
@d-healey So I tried that:
But I get the same errors.
It is still looking for the ipp. -
@VirtualVirgin Ok try scrolling down on that page and see if Use IPP Library is enabled (there are two use IPP options, disable both).
-
@d-healey Worked! Thank you!