Reason is just to get the fix for usb control callbacks so luftboot works again.
Since rcc_ppre1_frequency and rcc_ppre2_frequency were also renamed in the meantime, make appropriate changes.
[messages] replace BOOT with AUTOPILOT_VERSION
The AUTOPILOT_VERSION message contains:
- the version encoded as integer with `MAJOR * 10000 + MINOR * 100 + PATCH`
- the complete version string as returned by paparazzi_version
This message is sent once at startup of the autopilot, but can also be registered like any normal telemetry message by adding it to the telemetry airframe file.
The version string is also displayed in the GCS alert window (once per aircraft, unless it changes)...
Also the "build version" is not written to `var/build_version.txt` and the server also writes it to the log.
When building an aircraft it will now warn if the last build version differs from current version.
It only checks if the current version number (e.g. 5.3.2) is contained in the full build version string. So it will warn if you changed branches to a different version, but not after e.g. committing only a airframe config change.
You can also run `make print_version` to show the current version (and the warning if build version differs).
- always save build version when updating anything that depends on libpprz, so it will also be updated on e.g. make tmtc
- only warn if the version number (major.minor.patch) is different, disregard the label, sha1, dirty postfixes in the string...
The func of the HUP io watch returned false, meaning the event source was automatically removed.
This resulted in trying to remove a non existent source in the callback, which is bad as the id could already refer to something else...
And of course this was resulting in highly annoying warnings on every process that is automatically stopped/removed (like clean/build/upload):
GLib-CRITICAL **: Source ID xxx was not found when attempting to remove it
So by simply returning true to not automatically remove the event source this should be solved...
Since tcl8.6 "green" refers to same color as "darkgreen" (to the one used in web) and the former "green" is now "lime"...
But "lime" is not available in older versions, so hardcode the color to #00ff00
it would still be good to limit code line length to 100 when writing the code,
but setting this to something larger avoids stupid automatic wrappings that make things less readable...
most people want it to start at flightplan location anyway...
If someone wants to explicitly set the initial conditions, they can add whatever xml file they want...