Repository navigation
Refactor/multi arch - #17
Merged
Merged
Conversation
Replace the separate x86/ and arm/ Dockerfiles with one root Dockerfile built for linux/amd64 and linux/arm64 under a single tag, so users no longer pick between copter-X.X.X and copter-arm-X.X.X. - ARM-only build deps (pygame, lxml from source) gated on TARGETARCH - Clone ArduPilot on the build platform instead of under emulation - Skip the STM32 toolchain (DO_AP_STM_ENV=0); SITL doesn't need it and extracting it fails under QEMU on arm64 - Copy from lib/ directly, removing configure.sh and .gitignore - Drop linux/arm/v7: doubles emulated compile time for little use - CI builds both platforms per vehicle; crossBuild.sh and README updated
Michael-R-Dickinson
enabled auto-merge
October 30, 2026 23:07
orionblur
approved these changes
Oct 30, 2026
|
Lgtm |
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.
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves # (issue)
Type of change
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyHow Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code.