Code review comment for lp:~thomas-voss/mir/explicit-gcc-version
Revision history for this message
| Colin Watson (cjwatson) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
In the general case, until C++11 is stable at the toolchain level, it is possible that switching to a new compiler version may cause changes to exported symbols, requiring a SONAME change. It may therefore require source changes to projects using C++11 as well as simple rebuilds.
We don't want to have to coordinate changes to the default compiler version with things like SONAME changes in phone-related projects; it's better for those projects to be able to test the effects of this on their own schedule and do smaller coordinated transitions as required.
It remains necessary either way to coordinate changes to our C++11 projects, but at least this way it's trivial to grep the archive for the set of packages we need to worry about, and it's much easier to make sure that the compiler version change goes with a SONAME change if need be.