Put libraries into one libs directory under qgroundcontrol. Changed the neccessary files with references to those libraries.

Added a unit test, setAirframeTest. Changed setAirframe function. Added an end_of_enum to the airframe enum.

Unit tests compile and run but still fail 4 tests. Segfault fixed which was caused by colors list in UASInterface.h.

qgcunittest.pro now compiles and runs as long as run in terminal in projcts->Run Settings is unchecked.

as long as the waypoint comes from the right systemID there is no
point rejecting it based on component ID. 

The current_partner_compid is also completely wrong in the code, so
checking it makes no sense anyway

Refactored the LogCompressor. It wasn't properly handling certain message logging files that mixed messages (Issue #70).
One note is that this logger should work correctly as I've tested it, but could have some edge cases. It is pickier about the file format that it will sparse, but I don't know if the error-checking stuff from the old code would have actually worked. This can also be easily re-added.

This code is also much faster than the old stuff. From what I could tell it scanned through the log file at least twice, I think three times. It also copied a lot of data into memory instead of reading, processing, and writing one line at a time, so memory use should be much lower. Some memory leaks from the old code were also refactored out, so lifetime memory use should be down.

Fixed a couple of uninitialized arrays within the MAVLinkDecoder. It would result in weird time values in some data logging instances.

Replaced the autopilot-specific inclusion of MAVLink to be more generic. Now if you have no actual QGC modifications to make and just want your messages to be available for viewing/logging you can just create the user_config.pri file and override MAVLINK_CONF.

Also changed calculateRegression(...) to return a bool, as that's all it needs.