IPP on Windows 11 with VS 2022
-
@d-healey Yes. I tried all the "yes" options (yes, static linking, and dynamic linking) and all gave the same result.
-
Hi there! I'm new in this forum as well I'm new to HISE.
I'm having the same issues with Windows 10, VS 2022 (version 17.8.5) and IPP version 2021.10.0 . -
Unless you need IPP I'd just disable it.
-
@d-healey Sadly I do need IPP. I need to update a released project that uses the stock convolution module, so I don't think I have any other option.
-
@alber2000 Are you getting the same "could not expand the variable" errors?
At any rate, try an older version of IPP. 2020.0.166 is linked in this post and it worked for me on my Win 10 laptop (RIP). I used it with VS 2017 and 2022 without issue.
-
Bump bump... Still cannot get this to work. Has anyone managed to get IPP to work on Windows 11!? Really do not want to have to downgrade my new machine to Windows 10.
-
@ally said in IPP on Windows 11 with VS 2022:
Really do not want to have to downgrade my new machine to Windows 10.
If it comes to that, use a VM.
-
@ally I'm on W11 latest update. My Intel OneAPI installation is from around August 2023.
Everything works fine.
I suggest download VMPlayer and an image of Windows for VMWare from Microsoft's website (it comes with VS2022 preinstalled) and installing ipp there, then trying to build HISE. That should show you whether it's something on your end.
It might just be the latest Intel OneAPI update that doesn't play well with HISE/JUCE (the JUCE version in HISE seems to be old), there was an issue a few years ago when Intel consolidated all of its libraries into OneAPI, it just didn't work well with the JUCE version that was in HISE at the time, so someone here made an app that had links to all the old IPP downloads.
https://forum.hise.audio//post/33890
Also, this is IPP standalone.
I think this implementation in HISE/JUCE might be deprecated, though, and OneAPI package is mandatory.
-
@aaronventure Thank you so much for letting me know it's possible on Win11! I've tried numerous oneAPI and non-oneAPI versions and none have worked so far, but I did see this and this from Intel about needing to set environment variables with the setvars.bat script... do you remember doing that?
I tried it with and without and neither worked, but I definitely could've just done it wrong.
-
@ally no, I just did a basic install, nothing special.
-
@ally Did you try following along with my video?
-
@d-healey Yep, that's where I started. My HISE Projucer file had some changes (VS2022 exporter, no IPP paths, missing USE_IPP flag) so I put them in manually. Also tried using the VS2017 exporter + retargeting like in your video, as well as just using VS2017. No progress. At this point I'm pretty sure it's either a paths issue or an environment variables issue. Trying a VM is next on my list... hopefully that will give me some clues.
-
Just to update for anyone else who ends up with this issue, I still have not solved this. I downloaded the Windows 11 VM for VMWare from Microsoft with VS2022 preinstalled. Then I did a standard install of IPP 2021.10.2.7 (latest at the time) with Visual Studio integration and got the exact same issues.
The only bit of progress I've made is ruling out that it's caused by the "Could not expand IPP1A___ variable" errors. I installed the Intel oneAPI DPC++/C++ Compiler and those errors went away, but the rest of the IPP errors remained.
At this point I'm leaning towards a folder structure issue... I hear Intel likes to arbitrarily change how things are organized all the time, so I'm guessing that's it. I was able to scrounge up some older versions of IPP, but most are too old to install on Win 11. The only ones I can install are 2021.10.x and their folder structure is the same, so I still get all the "cannot open include file: 'ipp.h'" errors.
-
@ally Check out Aaron's post from a few days ago - https://forum.hise.audio/topic/9280/latest-ipp-2021-10-build-issues
