Win 10 / VS 2017 HISE Build Error

[DanH]

@DanH ok next error! The dreaded ipp...

3>c:\users\admin\desktop\hise-develop\hi_streaming\hi_streaming.h(77): fatal error C1083: Cannot open include file
       : 'ipp.h': No such file or directory (compiling source file ..\..\JuceLibraryCode\include_hi_modules_01.cpp) [D:
       \HALO-2-LAYOUT\Binaries\Builds\VisualStudio2017\HALO-2_SharedCode.vcxproj]

Since I installed ipp 2 years ago I have never had any problems with it at all, so until now everything should have been set up ok. I guess something may have changed...

I've never had any extra library search paths or anything, it's just always worked.

Will dig in the forum now but in case anyone has an immediate idea pls let me know!

[DabDab]

@DanH Do you compile VST from HISE or use Projucer > VS 2017 ?
If you open .jucer project after saving and opening with IDE just close Projucer. Sometimes this will remove ipp error.

[Dan Korneff]

@DanH I believe the file location of IPP changed when they released OneAPI, so newer HISE is probably looking in the newer location.

[DanH]

@Dan-Korneff just installed the OneAPI and got some more errors

[Dan Korneff]

@DanH I think you have to attach it in Visual Studio project properties

[DanH]

@Dan-Korneff thanks will have a crack!

[DanH]

@Dan-Korneff hmmm, well I don't even have the Intel Libraries option at all in the Config Properties... The OneAPI app says it's def installed though.

I'll try VS2022

[DanH]

@DanH ok well VS2022 didn’t help …. ‍️

[DanH]

@DanH ok well I 'repaired' the OneAPI install and tried to re-open the projucer project in VS2022 but I couldn't, it would only open in VS2017 (no option to open in 2022 no matter what I change in the projucer project).

And, for some reason the IPP library has now appeared in the project config menu in VS2017 (but NOT the OneAPI one!! - probs the old ipp library!), and I changed the setting from off to default linking and now it seems to be building something...

God knows what kind of frankenstein thing it will create but lets hope it exports plugins! :zombie:

[DanH]

@DanH god this is so insane. Hise has built. It opens. All seems ok. Begin exporting a vsti. It says that Hise has indeed been built with VS2022 (news to me) and that i need to change the project settings as I’m asking it to build with a different version of VS. Ok - do that. Try the export again - back to the ipp.h errors .

I mean, I built hise with ipp (apparently). Wtf is going on!

[DabDab]

@DanH You need to compile HISE with VS 2022. Keep only VS 2022 in your system.

Install IPP (One APi) after VS installation.

[DanH]

@DabDab yup using VS2022 after all it seems. Just reinstalled ipp using the offline installer and had an option to link it to VS2022. Currently looks a little happier executing an export. Will report back!

Thanks

[DanH]

@DanH well it exported fine it seems. Will give it a thorough check in the morning.

[Matt_SF]

@DanH Just an update : here @Dan-Korneff 's solution worked just fine. I followed @d-healey 's video, IPP was correctly installed, and setting it to 'Static Library' did the trick.

[DanH]

@Matt_SF thanks, managing to export ok again here. Weirdly projucer refuses to open the project in VS2022 (auto opens 2017 every time) so I have to do it manually.

Otherwise all good!

[d.healey]

@DanH Uninstall one, you don't need both.

[DanH]

@d-healey I will

[orange]

Guys I've just got a new Win 11 computer and will install everything from scratch.

Which one should I use, VS2017 or VS2022?

Is anyone using VS2022 without any issues?

[Matt_SF]

@orange VS17 works as usual here (but I'm on Win10) .

[DabDab]

@orange I have 3 Windows.. 2 Win 10 & One Windows 11. MS VS 2022 works very fine. If you have windows 11, I will recommend you MS VS 2022.