ardupilot/libraries/GCS_MAVLink/include/mavlink/v1.0
Gustavo Jose de Sousa 8cf54e1e3c GCS_MAVLink: standardize inclusion of libaries headers
This commit changes the way libraries headers are included in source files:

 - If the header is in the same directory the source belongs to, so the
 notation '#include ""' is used with the path relative to the directory
 containing the source.

 - If the header is outside the directory containing the source, then we use
 the notation '#include <>' with the path relative to libraries folder.

Some of the advantages of such approach:

 - Only one search path for libraries headers.

 - OSs like Windows may have a better lookup time.
2015-08-19 20:43:21 +09:00
..
ardupilotmega GCS_MAVLink: regenerate headers 2015-07-01 12:02:44 +10:00
common GCS_MAVLink: regenerate headers 2015-07-01 12:02:44 +10:00
checksum.h GCS_MAVLink: re-generate headers 2015-03-04 19:29:28 +11:00
mavlink_conversions.h GCS_MAVLink: re-generate headers 2015-03-04 19:29:28 +11:00
mavlink_helpers.h GCS_MAVLink: update from upstream headers 2015-05-25 12:20:27 +10:00
mavlink_protobuf_manager.hpp GCS_MAVLink: standardize inclusion of libaries headers 2015-08-19 20:43:21 +09:00
mavlink_types.h GCS_MAVLink: merged upstream header changes 2015-04-27 09:00:38 +10:00
protocol.h GCS_MAVLink: update from upstream headers 2015-05-25 12:20:27 +10:00