[Mesa-dev] [PATCH v5 0/3] build system: Unify c++11 detection and use

Gert Wollny gw.fossdev at gmail.com
Wed Oct 18 15:05:24 UTC 2017

Dear all,

here is another rework of the c++11 detection and flag application
implementing the ideas raised in the discussion with Emil and Chuck.

The part in configure.ac has been completely rewritten. Now one
can give an environment variable CXX11_CXXFLAGS to test for enabling
c++11 support with specific flags. Since in this case one can assume
that the users knows what they are doing, this test takes precedence.

If CXX11_CXXFLAGS is not given it will be tested whether c++11 is enabled
by default (like with g++ >= 6.0) and if not, the flag -std=c++11 is
tested. This has the advantage that for g++ >= 6 the whole of mesa will be
consistently compiled with the default standard (c++14) instead of forcing
one (in that moment older) standard on some parts of the code, while using
the newer standard for the rest were it is technically not needed.

I dropped the travis patch that added a build with g++4.4 because in the end
it only tested whether someone had force-set -std=c++11 somewhere.

best regards,

Submitter has no mesa-git write access.

Gert Wollny (3):
  configure+mesa/st: check for -std=c++11 support and enable
    mesa/st/test accordingly
  swr: Replace the check for c++11 by the unified version
  clover: use the unified check for c++11 instead of the gcc version

 configure.ac                                  | 67 ++++++++++++++++++++++++---
 src/gallium/drivers/swr/Makefile.am           |  4 +-
 src/gallium/state_trackers/clover/Makefile.am |  6 +--
 src/mesa/state_tracker/tests/Makefile.am      |  4 +-
 4 files changed, 69 insertions(+), 12 deletions(-)


More information about the mesa-dev mailing list