Mirror
/
ardupilot
mirror of https://github.com/ArduPilot/ardupilot
5
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ardupilot/mk/mavgen.mk

13 lines
1.1 KiB
Makefile
Raw Normal View History

mk: generate mavlink headers using mavlink module files
2016-01-02 01:03:59 -04:00
# mavlink header generation
MAVLINK_DIR := $(SKETCHBOOK)/modules/mavlink/
MESSAGE_DEFINITIONS := $(SKETCHBOOK)/modules/mavlink/message_definitions/v1.0
mk: fixed building with mavlink2 headers
2016-01-14 17:21:42 -04:00
MAVLINK_HEADERS := $(BUILDROOT)/libraries/GCS_MAVLink/include/mavlink/$(MAVLINK_SUBDIR)/ardupilotmega/mavlink.h $(wildcard $(BUILDROOT)/libraries/GCS_MAVLink/include/mavlink/$(MAVLINK_SUBDIR)/,*.h) $(wildcard $(BUILDROOT)/libraries/GCS_MAVLink/include/mavlink/$(MAVLINK_SUBDIR)/ardupilotmega,*.h)
MAVLINK_OUTPUT_DIR := $(BUILDROOT)/libraries/GCS_MAVLink/include/mavlink/$(MAVLINK_SUBDIR)
mk: generate mavlink headers using mavlink module files
2016-01-02 01:03:59 -04:00
mk: don't make mavlink generation depend on CHECK_MODULES this was causing a full rebuild every time, which is very annoying when developing
2016-05-16 00:33:00 -03:00
$(MAVLINK_HEADERS): $(MESSAGE_DEFINITIONS)/ardupilotmega.xml $(MESSAGE_DEFINITIONS)/common.xml
mk: generate mavlink headers using mavlink module files
2016-01-02 01:03:59 -04:00
echo "Generating MAVLink headers..."
#goto mavlink module directory and run the most recent generator script
echo "Generating C code using mavgen.py located at" $(SKETCHBOOK)/modules/mavlink/
mk: stop ignoring exit status of mavlink header generation Accept a 0 exit status, or a status >127 (indicating a signal caused the process to exit) as success. The original intent of ignoring the exit status was that the python executable was segfaulting after successfully building headers. Recently builds have been failing because people have not been doing recursive submodule updates, and the mavlink header generation has failed. Since we are ignoring the error the build rumbles on and fails later with a failed #include. This patch tightens our ignoring of a bad exit status to just signals. Note that the waf build system does the same check.
2016-11-06 20:40:25 -04:00
PYTHONPATH=$(MAVLINK_DIR) python $(MAVLINK_DIR)/pymavlink/tools/mavgen.py --lang=C --wire-protocol=$(MAVLINK_WIRE_PROTOCOL) --output=$(MAVLINK_OUTPUT_DIR) $(MESSAGE_DEFINITIONS)/ardupilotmega.xml; if [ $$? -le 0 -o $$? -gt 128 ]; then echo "mavgen: success"; exit 0; else echo "mavgen: failed"; exit 1; fi