Jg/221114 testbuild arm64 #461
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- the bin\release\* path is now bin\ARM64\* for target ARM64 -split target for plugins (depends if code is generated for it or not?)
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable target Windows 11 ARM64.
Minimal changes required to get it to compile for ARM64, with corresponding changes in setup.iss to cater for the "no, I won't set all subprojects to ARM64, some stay on Any CPU" behaviour. ARM64 builds in bin\ARM64\release instead of bin\release, and this requires some changes.
There are other artifacts in the .csproj files I have no explanation for, only that VS2022 ARM Preview may do this automatically.
The installation package works nicely here.