This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I try to figure out how to compile an EXE file (C++ project) for the "Windows on ARM" platform, using Visual Studio 2022:
Here is what I did so far:
But then the compilation always fails with:
I don't understand why that is :-(
As far as I can see, the "target machine" type is set correctly in Linker options:
I am unable to find any settings to explicitly specify the target machine in the "C/C++" compiler options, though. What am I missing ???
Thank you for any advice!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 12%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
It would appear that something is amiss with VS2022. I can reproduce your findings, but doing the same thing with VS2019 works fine.
If you can submit a bug report on it using the Report a Problem facility in VS, and post a link back here to your bug report, I'll verify it.
I have VS2017 installed too, no VS2019. Tried VS2017, just to be sure. But with VS2017 the error is the same as with VS2022.
I don't have 2017 installed.
Install the VS2019 (v142) toolset option in VS2022 - then change your project to use that toolset rather than v143. I believe that should have the same result as using VS2019.
I now installed VS2019, but with toolset "v142" I'm still getting the same error as before:
I'm not sure what's significantly different between us then.
I'd got a slightly older build of 2019, but I've now uninstalled it and instead installed the v142 toolsets for x86, x64, and ARM in VS2022, and again the v142 toolset works, while the v143 one shows the same LNK1112 problem you have.
MinxinYu-MSFT answer would appear to be correct. I'd totally missed the fact that the ARM tools aren't installed by default.
However the resultant error that mentions x86 is very misleading.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 57.00000000000001%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
Hi, @Gobi Todič
You need to install ARM build tools. Note: Clean the project before building.
Best regards,
Minxin Yu
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you! That was the problem, indeed.
I think it is a bit strange that even when "ARM build tools" are not installed, you can still select the "ARM" platform, but compilation will fail with a rather misleading error message.
Now I wonder: Does the "Windows on ARM" platform actually need ARM or ARM64 binaries ???
(I don't have such device at hand, so can not try it myself)
From this, I think it's ARM64 - though I've never encountered any such device.
Can ARM64 (64-Bit) devices run ARM (32-Bit) binaries, just like x86-64 (AMD64) devices can run x86 (i686) binaries?
The article I linked says:
Windows on Arm runs all x86, Arm32, and Arm64 UWP apps from the Microsoft Store. Arm32 and Arm64 apps run natively without any emulation, while x86 apps run under emulation.
But I have no experience of any such devices and haven't heard of any customers wanting software to work natively on Windows ARM devices either - though I suspect they'd be specific types of applications rather than anything I encounter.