ardupilot/libraries/GCS_MAVLink
tridge60@gmail.com ca8141cfb6 imported new MAVLink implementation
this new implementation reduces code size, and also reduces stack
usage, while avoiding the gcc union stack bug

Note that we will gain even more when we move to the new protocol
version, especially in terms of code size

git-svn-id: https://arducopter.googlecode.com/svn/trunk@3200 f9c3cf11-9bcb-44bc-f272-b75c42450872
2011-08-31 05:23:18 +00:00
..
doc Mavlink update 2011-02-11 11:04:52 +00:00
include imported new MAVLink implementation 2011-08-31 05:23:18 +00:00
message_definitions added SET_MAG_OFFSETS magnetometer message 2011-08-13 09:00:21 +00:00
missionlib MAVLink: added missing files from recent update 2011-08-13 06:30:29 +00:00
.gitignore MAVLink: added missing files from recent update 2011-08-13 06:30:29 +00:00
GCS_MAVLink.cpp Library wrapper for MAVLink protocol bits. 2010-11-25 06:38:18 +00:00
GCS_MAVLink.h imported new MAVLink implementation 2011-08-31 05:23:18 +00:00
license.txt MavLink Update 2011-02-08 23:16:58 +00:00
README Mavlink update 2011-03-16 10:09:22 +00:00
sync Updated GCS_MAVLink to match mavlink master. 2011-08-05 08:18:08 +00:00

MAVLink Micro Air Vehicle Message Marshalling Library

This is a library for lightweight communication between
Micro Air Vehicles (swarm) and/or ground control stations.
It serializes C-structs for serial channels and can be used with
any type of radio modem.

For help, please visit the mailing list: http://groups.google.com/group/mavlink

MAVLink is licensed under the terms of the Lesser General Public License of the Free Software Foundation (LGPL).
As MAVLink is a header-only library, compiling an application with it is considered "using the libary", not a derived work. MAVLink can therefore be used without limits in any closed-source application without publishing the source code of the closed-source application.

To generate/update packets, select mavlink_standard_message.xml
in the QGroundControl station settings view, select mavlink/include as
the output directory and click on "Save and Generate".
You will find the newly generated/updated message_xx.h files in
the mavlink/include/generated folder.

To use MAVLink, #include the <mavlink.h> file, not the individual
message files. In some cases you will have to add the main folder to the include search path as well. To be safe, we recommend these flags:

gcc -I mavlink/include -I mavlink/include/<your message set, e.g. common>

For more information, please visit:

http://qgroundcontrol.org/mavlink/

(c) 2009-2011 Lorenz Meier <mail@qgroundcontrol.org>