mixing the progress with stdout is causing problems for tools trying to consume stdout:
[update.py]: feature EF: Running (arm-none-eabi-nm --demangle --print-size /home/autotest/build/tmp/binaries.build/ZeroOneX6_Air/bin/blimp) in (.) (ZeroOneX6_Air,Blimp) not in build_options.py
[update.py]: feature EF: Running (strings /home/autotest/build/tmp/binaries.build/ZeroOneX6_Air/bin/blimp) in (.) (ZeroOneX6_Air,Blimp) not in build_options.py
Adds ability to pass --omit-ardupilot-keys to build_bootloaders.py
Adds ability to pass multiple public keys to the signing of the bootloader. This extends the functionality of the single key that was previously possible. All keys are prefixed with --signing-key and are appended to the args.signing_key array. All keys are checked for presense, and type before being used to sign the bootloader.
General tidy up of the argument parser, prints a proper description of the role of the file.
This fixes make_secure_bl writing to the incorrect file (sys.argv[1]). The resultant file was whatever argv[1] was passed in as, which could have been --omit-ardupilot-keys.
This fixes make_secure_fw not running at all because of a possible return outside of a function. Also improves argument passing so we can get ourselves a better help file.
Ensures that all new boards added via PR include documentation by checking
for the presence of a README.md file in the hwdef directory. This helps
maintain code quality and provides essential information for users.
AP_Periph boards are excluded from this requirement as they typically don't
need the same level of user-facing documentation.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add a script that:
- Finds all newly-added hwdef files in the current branch (git status 'A')
- Extracts board names from hwdef directory paths
- Builds each new board and its bootloader if a bootloader hwdef was added
- Skips ESP32 boards (CI limitation)
- Uses BuildScriptBase for common build operations
The script is designed to run in CI to ensure new board definitions compile correctly.
Create a base class for build scripts that provides common utilities extracted from size_compare_branches.py:
- run_program(): Execute commands with output handling
- run_waf(): Run waf with consistent build environment
- run_git(): Run git commands
- find_current_git_branch_or_sha1(): Get current branch/SHA
- find_git_branch_merge_base(): Find merge base
Refactor size_compare_branches.py to use the base class, reducing duplicated code.
Other scripts with similar patterns can be refactored in the future:
- build_binaries.py
- build_bootloaders.py
- build_iofirmware.py
- build_peripherals.py
- configure_all.py
autotest: test_build_options.py: do not test AP_PERIPH_* defines on non-Periph builds
test_build_options.py: AP_ROVER_AUTO_ARM_ONCE_ENABLED is only on Rover
test_build_options.py: create and use a blacklist
options on this blacklist really can't be tested when we're doing the
disable-everything step as they require one of two other options to
work, and we can't represent that in our dependencies
Tools: build_options.py: correct dependencies for CRSF Scripting
Tools: extract_features.py: correct extraction of AP_MAVLINK_FTP_ENABLED
Tools: test_build_options.py: exempt EK3_FEATURE_OPTFLOW_SRTM on some vehicles
AP_Terrain isn't instantiated so the symbol (and feature!) are missing
build_options.py: add missing dependency for Cortex generator
autotest: test_build_options.py: most vehicles do not have AP_ADSB_AVOIDANCE_ENABLED
autotest: test_build_options.py: fix for AP_SCRIPTING_BINDING_MOTORS_ENABLED
test_build_options.py: exempt AP_MOTORS_TRI_ENABLED except on Copter
Plane only has this if quadplane is enabled...
e.g.:
./Tools/autotest/vehicle_test_suite.py:8607:89: B006 Do not use mutable data structures for argument defaults. They are created during function definition time. All calls to the function reuse this one instance of that data structure, persisting changes between them.
e.g.
./Tools/scripts/param_check_all.py:180:40: B008 Do not perform function calls in argument defaults. The call is performed only once at function definition time. All calls to your function will reuse the result of that definition-time function call. If this is intended, assign the function call to a module-level variable and use that variable as a default value.
Peter Barker
James O'Shannessy
Randy Mackay
Bob Long
Andy Piper
MinderringandHenry Wurzburg
bnsgeyer
Oliver Walters
Thomas Watson
Erkan Vatan
Andrew Tridgell
Tom Pittenger
Christian Clauss