Re:Breaking all the Eggs in C++ (2015)
by jcelerier on Sunday December 30, 2018 @12:14PM
(#18790125)
you can just include Qt with -isystem instead of -I, it will disable warnings for those headers
[ Parent
| on HN ]
Re:Breaking all the Eggs in C++ (2015)
by hermitdev on Sunday December 30, 2018 @04:56PM
(#18791586)
Definitely recommend using -isystem for third party libs such as Boost, ACE, QT, Protobuf, etc. I strive for warning free code in my own, but dont have much control over the libs I use. Warnings from Protobuf are especially annoying due to Googles ill-thought-out disregard for signed/unsigned comparison (and their bullshit rationale in their style guideline) and continued use of NULL/0 as a nullptr constant (they only support C++11 and greater, no reason to not use nullptr now). I strive for clean compilation with "-Wall -Wextra -Wzero-as-null-pointer-constant -Werror", but alas, hard to implement after the fact in legacy code.
Re:Breaking all the Eggs in C++ (2015)
by AlexanderDhoore on Sunday December 30, 2018 @12:26PM
(#18790204)
Thx I will try this!
EDIT Docs about this: https://gcc.gnu.org/onlinedocs/cpp/System-Headers.html