Commit Graph

7 Commits

Author SHA1 Message Date
Peter Barker e94c23e0a1 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-16 00:08:49 +00:00
Andrew Tridgell b0be3e7423 mk: fixed building with mavlink2 headers 2016-05-21 15:25:12 +10:00
Andrew Tridgell 8ec0e687db 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 17:22:11 +10:00
Lucas De Marchi a38d350502 mk: fix mavgen dependency
The rule to generate mavgen headers need to depend on the rule to check
the submodules, otherwise they can execute in parallel and the
(mavlink) submodule be updated while the headers are generated.
2016-05-10 10:57:49 -03:00
Tom Pittenger 7fda3ba178 mk: fix SITL windows build
fixes https://github.com/diydrones/ardupilot/issues/3586
2016-02-15 16:42:06 -08:00
Andrew Tridgell f6c2b55c3f mk: fixed dependency on mavlink header generation 2016-01-15 07:44:15 +11:00
Siddharth Bharat Purohit dd65495668 mk: generate mavlink headers using mavlink module files 2016-01-15 07:28:47 +11:00