Lexical or Preprocessor Issue - "ipp.h" file not found
-
@d-healey Thanks! I thought that was the problem.
In the meantime I found an old version of IPP uploaded by @DanH which made my day! Not errore anymore! I hope @DanH will allow me to share the link here in case someone else will have the same problem: https://www.dropbox.com/sh/4gx74wg1jpfnk7r/AACkGmy8SdV-j0qsiw5VFYFza?dl=0
-
@Maichol with Catalina you have to move folders from / opt / intel / ipp and it will work.
-
@yall do you mean that the paths should be?:
- Header search paths: /opt/intel/ipp
- Extra library search paths: /opt/intel/ipp
So you're using Catalina, the v12.4 Xcode and the latest IPP?
-
@Maichol I just read that you downloaded the latest version of ipp as a first step. I had encountered the same problem as you at the beginning.
in fact, when you go to projucer in the export module it seems to me, you have all the paths which correspond to ipp either / opt / intel / ....
if you check these paths in your mac having downloaded the latest version of IPP, you would not get the same paths. that's why you have to move the folders to / opt / intel .... I'm writing this from memory I don't have my mac handy to check. but try looking at the paths in projucer, then check in mac search if the paths match. older versions of IPP went straight to the right place, but the newer version hides in another folder. -
@Maichol i am using catalina and xcode 11.3 i believe. (I only use mac to export my plugins created under windows which is much faster ^^)
I did not manage to compile with xcode 12.2 -
@yall Ok, I think now I get what you mean. The path in my Mac was something like "/opt/intel/2021.1/ipp" (I'm writing this from memory too since I installed the old version of IPP and everything works now) and I tried to change the path in Projucer with this one but it didn't work. Maybe I should have done the opposite like you said, moving the ipp folder directly into the intel folder to match the path of my Mac to the one in Projucer (if I understood right).
Anyway, now it's working with the old IPP, do you think it would be better to have the latest version? or it's the same?
Thanks for your time!
-
@Maichol I do not know. I suppose the more recent the better ^^ if you have a 1980 ipp version, the 2019 will necessarily be better ^^
-
@Maichol Yes you have to do the opposite and move the folders, leaving the path in Projucer as is. This will get HISE to compile but I think compiling plugins will still fail (certainly does on Windows). Stick with the old version until someone finds a solution.
-
@yall said in Lexical or Preprocessor Issue - "ipp.h" file not found:
if you have a 1980 ipp version, the 2019 will necessarily be better ^^
I prefer 1933 King Kong to 2005 King Kong. Newer is not always better
-
@d-healey It's true, let's take the example of polar bears, it was better before ^^
-
@d-healey said in Lexical or Preprocessor Issue - "ipp.h" file not found:
I prefer 1933 King Kong to 2005 King Kong. Newer is not always better
Good point!ahah
Just for the science I tried 2020 IPP with 12.4 Xcode and it doesn't work. So I think I'll stick with this IPP but with an older Xcode since it was working before.
-
@d-healey
Hi David, I'm attempting to build Hise without IPP on Mojave.
I just downloaded the scriptnode branch, and without changing anything, the jucer file looks like this:
USE_IPP=0 looks like what I want.
When I try to build in Xcode I get this though:
Perhaps IPP needs to be turned off somewhere else...
I know that in the hi_core there's an IPP option, and I see that it's enabled there actually!
When I tried disabling IPP here I got the same error messages.
I wonder if there may be somewhere else where I need to disable IPP? -
@benosterhouse I also have HISE running on a Mac under Mojave - Took me a while to figure it out
I see you have selected "Xcode (iOS)" in the Projucer - is that intentional?
-
@benosterhouse Here my Settings - without ipp - Maybe it helps
Mojave 10.14.6
Projucer 5.4.5
Xcode 10.3
-
No that was not intentional. Thank you, trying this now...
-
Ok, it finished building, and it worked on the first try with those settings!
Thanks again
-
@benosterhouse You are welcome
I bought your Sospiro Strings last year - very nice
Now Hise - no more Kontakt? -
Glad to hear it
I'm still working in Kontakt of course, but am considering the benefits of hise for future projects.I was thinking of putting out a vst version of Sospiro alongside the kontakt version, and seeing how many people get the kontakt version vs. the vst.
-
This sounds interesting and would also interest me if people would rather have a VST or a Kontakt version.
I'm sure I have around 250 Kontakt libraries outside of the ones already supplied by Ni with Komplete 13.
And I personally hate and love Kontakt. -
Yeah --it might be the case that more people want to stick within the familiarity of kontakt and other major samplers. I don't know. I should probably have done more research before diving in
But, it'd be nice to at least get this one vst out there.
