Comment 4 for bug 1488079

On 2015-08-24 15:10 (+0200), Alex Valavanis wrote:
> A proper fix would enforce C++11 builds for everyone, but this is
> problematic, because AFAIK older OS X releases don't provide
> compiler support for C++11.

1) Just adding the compile flag '-std=c++11' won't break trunk builds on OS X 10.7 - as long as Inkscape doesn't actually _use_ c++11 features.

Updating to future stable releases of the C++ libs (glibmm, libsigc++, atkmm, pangomm, cairomm) though won't work on OS X 10.7.5 with the system tool-chain (and AFAICT won't really be an option anyway even if a full tool-chain with C++11 would be compiled from source, because the next stable release of glib2 (2.46) will only support OS X 10.9 and later).

So far Inkscape does not require the most latest stable releases of glib/glibmm (configure.ac checks for 2.28) - is this requirement going to change soon due to internal changes in Inkscape?

2) The system tool-chain provided on older versions of Mac OS X (Jon Cruz' 10.6, and LiamW's 10.5 for 32bit packages) likely does not even support adding the compiler flag '-std=c++11' unconditionally. On those systems, a custom tool-chain would have to be compiled from source, and used for inkscape and all dependent C++ packages (the same caveat wrt next major stable glib release applies here too).