Hello Ian, Thank you for taking your time to reply. I was aware of the grep possibility. However altering the output of my compiler really is something I'd rather not do. I'm sure there are cases where ignoring lines from the compiler would really cause confusion and endless hours trying to find the cause of the issue. Eventually, I ended up placing the third party in a static lib, and statically linking my project to it. The static library I configured to build without warnings. Best regards, Ian Lance Taylor-3 wrote: > > Zadirion <zadirion@xxxxxxxxx> writes: > >> I've come across an interesting dilemma: >> given the following project structure >> ./myproject/main.cpp >> ./thirdpartylib/source.cpp >> ./thirdpartylib/header.h >> >> I need to ignore the warnings in the third party library. > > Use grep -v on the compiler output? > > I don't think there is any way to tell gcc to ignore the warnings from a > specific set of header files. > > Ian > > -- View this message in context: http://old.nabble.com/-isystem-and-local-includes-tp30211832p30225602.html Sent from the gcc - Help mailing list archive at Nabble.com.
