# TIP: Intel IPP with Visual Studio C++ under Windows ARM for x64 builds

**URL:** <https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637>\
**Category:** Windows\
**Created:** [March 26, 2025, 11:38am UTC](https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637 "2025-03-26T11:38:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chkn](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/chkn/32/3862_2.png) [@chkn](https://forum.juce.com/u/chkn)\
**Post date:** [March 26, 2025, 11:38am UTC](https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637/1 "2025-03-26T11:38:58Z")

</div>

This is a tip using Intel IPP libraries, if you are developing x64 binaries, inside a parallels VM on Apple Silicon, with Windows 11 Arm and Visual Studio Arm.

The latest Intel IPP setup doesn’t install correctly inside the latest Visual Studio Community on Arm, more precisely the Intel IPP extension doesn’t install, the libraries itself can be used to compile a x64 binary.

This example uses static library/sequential execution mode, for other modes you have include different libraries/use other preprocessor definitions.

→ “Extra Preprocessor Definitions”  
\_IPP\_SEQUENTIAL\_STATIC

→ “External Libraries to Link”  
C:\Program Files (x86)\Intel\oneAPI\ipp\2021.6.0\lib\intel64\ippimt.lib  
C:\Program Files (x86)\Intel\oneAPI\ipp\2021.6.0\lib\intel64\ippsmt.lib  
C:\Program Files (x86)\Intel\oneAPI\ipp\2021.6.0\lib\intel64\ippcoremt.lib

→ “External Library Search Paths”  
C:\Program Files (x86)\Intel\oneAPI\ipp\2021.6.0\lib\intel64

---

<div class="post-metadata">

**Author:** ![chkn](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/chkn/32/3862_2.png) [@chkn](https://forum.juce.com/u/chkn)\
**Post date:** [July 10, 2025, 8:55am UTC](https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637/2 "2025-07-10T08:55:17Z")

</div>

Does anybody else tried to develop x64 binaries, inside a parallels VM on Apple Silicon, with Windows 11 Arm and Visual Studio Arm? Or am I the only crazy one? Its actually sufficient fast.

I have to admit that I only use Xcode when it is absolutely necessary (feels slow and uncomfortable), and I have not yet dared to use VSCode/CMake.  
Mostly I use Visual Studio Community on a separate Windows machine these days. Super comfy and fast.

---

<div class="post-metadata">

**Author:** ![kunz](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kunz](https://forum.juce.com/u/kunz)\
**Post date:** [July 10, 2025, 6:05pm UTC](https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637/3 "2025-07-10T18:05:54Z")

</div>

I will use Parallels and create x64 binaries on Windows ARM as soon as I can sign AAX plugins with iLok in this environment. But I just run the cmake file to create the plugins. I use CLion on macOS for the development.

I did some tests a few months ago and was able to build x64 without any problems. I think I had installed the normal x64 visual studio for this. I’m using the VS Clang compiler on windows. Don’t use Intel IPP

---

<div class="post-metadata">

**Author:** ![chkn](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/chkn/32/3862_2.png) [@chkn](https://forum.juce.com/u/chkn)\
**Post date:** [March 19, 2026, 1:25pm UTC](https://forum.juce.com/t/tip-intel-ipp-with-visual-studio-c-under-windows-arm-for-x64-builds/65637/4 "2026-03-19T13:25:04Z")

</div>

I forgot to mention:

Header Search Path:  
C:\Program Files (x86)\Intel\oneAPI\ipp\2021.6.0\include