- 17 Feb, 2014 4 commits
-
-
Julian Oes authored
-
Julian Oes authored
-
Julian Oes authored
-
Lorenz Meier authored
-
- 16 Feb, 2014 3 commits
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
Add new waypoints based on the UAV airframe type
-
- 15 Feb, 2014 13 commits
-
-
Don Gagne authored
Reverted windows build change from ThirdPartyWarnings merge
-
Don Gagne authored
-
Lorenz Meier authored
Third party warnings
-
Don Gagne authored
Merge branch 'ThirdPartyWarnings' of https://github.com/DonLakeFlyer/qgroundcontrol into ThirdPartyWarnings
-
Don Gagne authored
-
Don Gagne authored
Not going to fix these two warnings in Windows builds so silence from makefile
-
Don Gagne authored
Use a pragma around our use of that header to silence the warning. OSG 3.01 has these warnings, 3.2 has fixed them, but 3.2 doesn’t isn’t the widely used release yet. So at some point when we upgrade to 3.2 this will no longer be needed.
-
Don Gagne authored
qserialport and qextserialport use the pattern of += into PUBLIC_HEADERS and PRIVATE_HEADERS. This leads to the same header being included twice. Which in turn causes the rule for moc in the makefile to be added twice, hence the warning. Using *= instead of += removes the duplication.
-
Don Gagne authored
The latest version of qwt does have these warnings fixed. But the latest version also has removed some deprecated printing functionality which we are currently using. I gave a try at updating but it looked fairly involved and over my level of understanding for that part of the code. So pragmas for now. When someone does upgrade qwt the pragmas will no longer be needed.
-
Don Gagne authored
I looked at the latest version of opmapcontrol in OpenPilot. This has not yet been fixed. So added pragma to silence.
-
Don Gagne authored
Either this location is incorrect, or it is an optional install that I haven’t figured out how to get yet. Either way, this is failing TeamCity Windows Releases builds which I want to turn on. So for now, I’m disabling. I’ll figure out how to make it work correctly with my work on generating windows installs.
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- 14 Feb, 2014 10 commits
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
Disable the active WP setting in the edit list, as its super error prone - only allow it in the view list and switch between views based on activity on the system / UI
-
Lorenz Meier authored
-
Lorenz Meier authored
-
- 13 Feb, 2014 10 commits
-
-
Thomas Gubler authored
-
Thomas Gubler authored
-
Don Gagne authored
Not going to fix these two warnings in Windows builds so silence from makefile
-
Don Gagne authored
Use a pragma around our use of that header to silence the warning. OSG 3.01 has these warnings, 3.2 has fixed them, but 3.2 doesn’t isn’t the widely used release yet. So at some point when we upgrade to 3.2 this will no longer be needed.
-
Don Gagne authored
qserialport and qextserialport use the pattern of += into PUBLIC_HEADERS and PRIVATE_HEADERS. This leads to the same header being included twice. Which in turn causes the rule for moc in the makefile to be added twice, hence the warning. Using *= instead of += removes the duplication.
-
Don Gagne authored
The latest version of qwt does have these warnings fixed. But the latest version also has removed some deprecated printing functionality which we are currently using. I gave a try at updating but it looked fairly involved and over my level of understanding for that part of the code. So pragmas for now. When someone does upgrade qwt the pragmas will no longer be needed.
-
Don Gagne authored
I looked at the latest version of opmapcontrol in OpenPilot. This has not yet been fixed. So added pragma to silence.
-
Don Gagne authored
Either this location is incorrect, or it is an optional install that I haven’t figured out how to get yet. Either way, this is failing TeamCity Windows Releases builds which I want to turn on. So for now, I’m disabling. I’ll figure out how to make it work correctly with my work on generating windows installs.
-
Lorenz Meier authored
-
Lorenz Meier authored
-