This fix was pulled across from current QSerialPort codebase. I looked
into pulling across newer version of full QSerialPort. While doing that
I discovered that the version we are using has already been hacked to
work with us. It was fairly involved to redo those hacks. So decided to
pull individual change across instead since our version is already not
clean. When we switch to Qt5 all this will go away.
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.
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.
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.
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.
This removes a race condition between both qwt and qt against math.h on
windows with _USE_MATH_DEFINES set. If math.h comes after qwt or qt
math headers the math defines will be redefined. Really nasty to track
down and ordering problems. So instead I just removed using math
defines on windows and fall back to asin definition of M_PI_2. This
will have some slight perf impact since it calls function instead of
using constant. But I doubt on any of today’s machine it really makes a
difference.
Start move to single column layout for advanced parameters; Fix
crashing bug in PrimaryFlightDisplay when uas is removed and then
re-added; workaround compiler warning in GeneralBlockPanelKernel,
WillRam
Thomas Gubler
Don Gagne
Bryant
Lorenz Meier
tstellanova
Michael Carpenter
Bill Bonney
Matthias Krebs
Stefano Probst
barthess