Comment 8 for bug 1488079
Revision history for this message
| su_v (suv-lp) wrote Re: Inkscape won't compile against libsigc++-2.5.1 due to missing "-std=c++11". | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Alex - agreed. AFAIU separate tests for:
* sigc++-2.0 >= 2.5.1
* glibmm >= 2.45.31
are likely sufficient to detect the requirement for c++11 in Inkscape's CXXFLAGS.
AFAICT the other C++ bindings depend directly or indirectly on glibmm, and will require c++11 if glibmm does. Older versions than the following releases can't be provided by the system if glibmm was already upgraded:
* atkmm >= 2.23.2
* pangomm >= 2.37.1
* gtkmm3 >= 3.17.41 [1][2]
Cairomm seems to be different: the library itself requires c++11 lately
* cairomm >= 1.11.4
but apparently older versions of cairomm may still work ok with newer C++ bindings:
https:/
OTOH current stable gtkmm 3.18 now requires cairomm >= 1.12.0 (or rather gdkmm does):
https:/
--
[1] Legacy gtkmm 2.24 (see branch in git) needs to be built with c++11 if compiled against newer glibmm, but does not require it for itself:
https:/
https:/
[2] Current stable gtkmm 3.18 has these direct requirements:
* giomm-2.4 >= 2.46.1
* pangomm-1.4 >= 2.38.1
* gtk+-3.0 >= 3.18.0
* cairomm-1.0 >= 1.12.0
* gdk-pixbuf-2.0 >= 2.26.0
* atkmm-1.6 >= 2.24.1
glibmm 2.46.1 (for giomm) adds the direct requirement for
* sigc++-2.0 >= 2.6.0