Well, Compress-DSRC-0.002/Build.PL uses Module::Build::WithXSpp which uses ExtUtils::CppGuess
It is those modules that need enhancing not your Build.PL, so you can simply tell them you want C++11, without having to use extra_compiler_flags -std=c++11 or ... in your Build.PL
But speaking generically,
Yes, %Config is where you're supposed to retrieve the compiler name, compiler options..... used to build perl, they're going to be used to build your module as well
If a user is going to use a different compiler, hes going to override %Config with ExtUtils::FakeConfig ...
Sure, print an extra message to make it easy for user to understand that it probably won't work; compiler messages can be hard to understand
But you shouldn't prevent the compiler from trying
Only the compiler knows for sure if it supports C++11
Best option is to let the compiler try
In reply to Re^3: Check compiler features before building XS module ( extra_compiler_flags -std=c++11 )
by Anonymous Monk
in thread Check compiler features before building XS module
by jdv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |