Conversation
…for native context
…Build with msbuildLocation
…guration vcvarsall.bat only supports x86/amd64 host architectures. ARM64 builds work because CMake auto-detects Hostarm64/arm64/cl.exe and MSBuild invoked via SysNative uses the native ARM64 toolchain.
Instead of waiting for image rebuilds, patch the agent at pipeline start: - Detects agent at C:\vss-agent\<version> - Checks PE header for architecture - Downloads matching ARM64 version if needed - Extracts with overwrite, preserving config - Only runs on ARM64 jobs
…ion step - Add build/docs/ARM64-AGENT-PATCHING.md with full explanation of the problem, approaches tried, and current solution using 1ES provisioning script - Update Setup.ps1 (v1.3.0) with detailed step-by-step documentation, log location, and troubleshooting info - Remove runtime agent patching (cannot work - files locked by running agent) - Replace with architecture verification step that fails with clear instructions if agent is not ARM64
With the 1ES provisioning script patching the agent to ARM64: - No more WoW64 emulation to escape - Standard vcvarsall works for all architectures - Standard MSBuild task works for all architectures - Removed escape-wow64.yml template - Simplified setup-vcvars.yml and build-solution.yml - Removed isArm64 flags from architecture definitions - Changed vcvarsArg from 'arm64_arm64' to 'arm64' (native host)
All templates were just single-task wrappers after removing WoW64 logic. Inline vcvarsall and MSBuild directly in devops.yml for clarity.
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
d94a4d4 to
ab0a65e
Compare
Author
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
- Rename ARM64-AGENT-PATCHING.md to arm64-agent-patching.md (per dcristo nitpick) - Update comment to clarify vcvarsall is needed for both CMake and MSBuild
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or 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
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.
No description provided.