1 | | Yeah, I'm not so sure about that now that I look at it -- this would be happening while the build line is being parsed, so would it work to push back the `std=` onto the build line again? Would it get re-parsed? |
2 | | |
3 | | Perhaps you'd have to find out what `-std=c++11` invokes when being parsed, and do that. Is setting this enough, I wonder: |
4 | | {{{ |
5 | | Opts.CPlusPlus11 = Std.isCPlusPlus11() |
6 | | }}} |
7 | | |
8 | | There might be more to it. |
9 | | |
10 | | And then what if there is some other `-std=` line on the build line? Presumably that should win. |
11 | | |
12 | | Enough speculation, I guess. Have to dig in and try different things to sort this out. |
| 1 | See below for the more likely area to patch, if desired. |