nappgui_src icon indicating copy to clipboard operation
nappgui_src copied to clipboard

Build for ARM64 on Windows 11

Open d33p-dev opened this issue 1 year ago • 5 comments

Hi @frang75 , I posted in Discord but surfacing here bc others might see the issue here more easily than the discord channel.

I'm trying to build on Win11 ARM and get the following error:

error : The BaseOutputPath/OutputPath property is not set for project 'VCTargetsPath.vcxproj'.

Here's the complete build log:

`c:\Work\Dev\Deep\DeepNative\nappgui_src>cmake -S . -B build -- Building for: Visual Studio 17 2022 -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22621. CMake Error at CMakeLists.txt:14 (project): Failed to run MSBuild command:

C:/Program Files/Microsoft Visual Studio/2022/Community/MSBuild/Current/Bin/arm64/MSBuild.exe

to get the value of VCTargetsPath:

MSBuild version 17.9.8+b34f75857 for .NET Framework
Build started 7/16/2024 9:01:41 AM.

Project "C:\Work\Dev\Deep\DeepNative\nappgui_src\build\CMakeFiles\3.28.1\VCTargetsPath.vcxproj" on node 1 (default targets).
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\arm64\Microsoft.Common.CurrentVersion.targets(839,5): error : The BaseOutputPath/OutputPath property is not set for project 'VCTargetsPath.vcxproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='ARM64'.  You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. [C:\Work\Dev\Deep\DeepNative\nappgui_src\build\CMakeFiles\3.28.1\VCTargetsPath.vcxproj]
Done Building Project "C:\Work\Dev\Deep\DeepNative\nappgui_src\build\CMakeFiles\3.28.1\VCTargetsPath.vcxproj" (default targets) -- FAILED.

Build FAILED.

"C:\Work\Dev\Deep\DeepNative\nappgui_src\build\CMakeFiles\3.28.1\VCTargetsPath.vcxproj" (default target) (1) ->
(_CheckForInvalidConfigurationAndPlatform target) ->
  C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\arm64\Microsoft.Common.CurrentVersion.targets(8`

d33p-dev avatar Jul 16 '24 13:07 d33p-dev

I'm checking contents of VCTargetsPath and it looks correct to me.... Debug configuration / ARM64 platform. But, I'm not sure why it says Visual Studio 2022 (v143) (not installed)... I have the Win32 C/C++ and Windows 10 SDK workloads / features installed in my VM with VS 2022. I'll look around maybe I'm missing some features in the VS install...

Screenshot 2024-07-16 at 9 17 58 AM

d33p-dev avatar Jul 16 '24 13:07 d33p-dev

Ok, I think I was missing the latest v143 ARM build tools for C/C++.... Adding it now and will try to rebuild NApp.

d33p-dev avatar Jul 16 '24 13:07 d33p-dev

Hi @d33p-dev! I have never compiled NAppGUI in Win-ARM and its not "officially" supported by build system. I'll set up a Win-ARM build node ASAP and test this configuration.

frang75 avatar Jul 16 '24 18:07 frang75

Man, I just went down the RABBIT HOLE with this.... I tried to install the workload (build tools) for ARM builds for C/C++ and they installed but then VS itself would not load without throwing up error messages "package blah blah did not load". It would not run at all after I installed/added the ARM build tools. I literally had to delete the entire VM, create a new one and go through the 13GB (!!!!!! TF) install for VS2022 with C/C++ support. It just finished so this is now a clean VM / Win11 and I'm going to try and build NApp on it for ARM.

Whoa... VS2022 is a mess

d33p-dev avatar Jul 16 '24 19:07 d33p-dev

Update: https://github.com/frang75/nappgui_src/pull/190

frang75 avatar Mar 08 '25 08:03 frang75