[build] Annoying warnings from Asio, -isystem from bjam?
When I have "-Wunused-variable" I get these highly annoying warnings from boost/asio/error.hpp which I'm sure almost everyone has seen: boost_1_60_0/boost/asio/error.hpp:258:45: warning: ‘boost::asio::error::system_category’ defined but not used [-Wunused-variable] static const boost::system::error_category& system_category I don't want to disable the warning but I also don't want the false positives. Thankfully, clang and gcc have this wonderful option "-isystem" which lets you mark include paths as belonging to the system. This prevents warnings from being emitted that the programmer can do nothing about. How can I get Boost.Build to add the Boost library header search paths using "-isystem" so that gcc doesn't report warnings in Boost headers that I cannot do anything about? More detail here: http://stackoverflow.com/questions/1867065/how-to-suppress-gcc-warnings-from... I've played around with <sysinclude> but can't seem to figure it out. Here's my Jamroot (my project builds on its own, without putting it in the Boost tree): https://github.com/vinniefalco/Beast/blob/master/Jamroot#L80 -- Follow me on Github: https://github.com/vinniefalco
On 11/03/16 02:00, Vinnie Falco wrote:
When I have "-Wunused-variable" I get these highly annoying warnings from boost/asio/error.hpp which I'm sure almost everyone has seen:
boost_1_60_0/boost/asio/error.hpp:258:45: warning: ‘boost::asio::error::system_category’ defined but not used [-Wunused-variable] static const boost::system::error_category& system_category
There's this PR fixing it: https://github.com/boostorg/asio/pull/32
On Wed, Nov 2, 2016 at 7:23 PM, Andrey Semashev
There's this PR fixing it:
Yep, but we're coming up on the 1-year anniversary of that pull request, giving me little confidence it will be merged soon or if at all. That's why I'm trying to resolve the problem in my own build scripts.
participants (2)
-
Andrey Semashev
-
Vinnie Falco