-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Remove MAVLink development.xml dialect from default targets, add specific ones #25834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: -1280 byte (-0.06 %)]px4_fmu-v6x [Total VM Diff: -1344 byte (-0.07 %)]Updated: 2025-11-21T07:59:51 |
0641a99 to
0fc3573
Compare
0fc3573 to
fda07f0
Compare
|
CI failures are real
|
|
Yep I know... working on it: mavlink/MAVSDK#2709. |
We should not build and release with the MAVLink development dialect because messages in development.xml can change at any time and break things. Instead we should prototype and test things using specific mavlink-dev targets.
These targets can be used to test MAVLink messages in the development.xml dialect.
And update submodule.
This should now include the figure eight messages.
fda07f0 to
c38ee7f
Compare
|
@hamishwillee I just checked and it turns out CI automatically builds/checks all board variants, so the |
We should not build and release with the MAVLink development dialect because messages in development.xml can change at any time and break things.
Instead we should prototype and test things using specific mavlink-dev targets.