mavlink/mavlink — Issue #10: Message Definition Confusion
Author: TobiasSimon
Created: 2012-02-16 09:03:05+00:00
State: open

Hi Everyone!

I'm wondering why there are at least 3 different locations in which the mavlink message definitions reside. When I use "diff" on these 3 different locations (mavlink, pymavlink and qgroundcontrol), I find three different common.xml files :-( This could lead to a lot of confusion, especially when generated code is also checked-in.
One solution for eliminating at least one clone would be to integrate pymavlink and mavlink. For qgroundcontrol - maybe a git submodule might help? (I know, submodules have some flaws...)

What is your opinion regarding this?
Regards,
Tobias