< fanquake>
Qt 5.12.6, even though it's advertised as being able to be built with c++11, actually requires c++14 on macOS...
< fanquake>
Apparently building with c++11 is considered a "corner case
< fanquake>
"Building Qt requires C+11, at a minimum, but in practice we use later features, usually under a feature define, or with a fallback of some kind. On platforms that support > C11, we've (apparently) not considered the fallback necessary, under the assumption C+14 is always available."
< ysangkok>
but c++14 is available everywhere (even centOS). it seems the only reason bitcoin core didn't upgrade to c++14 is because people want to have less bumps and the next bump should therefore be c++17 as it is a feature upgrade and not a "nits issue"
< luke-jr>
fanquake: the real question is if Qt applications can be built with C++11
< bitcoin-git>
[bitcoin] hebasto opened pull request #17696: qt: Force set nPruneSize in QSettings after the intro dialog (master...20191208-prune-settings-override) https://github.com/bitcoin/bitcoin/pull/17696
< elichai2>
fanquake: is this a single missing feature define? if so maybe we could patch upstream for that
< elichai2>
if they say they want to support C++11 then they should be glad to accept the patch(hopefully)