Compatibility is dead
Daniel van Vugt
daniel.van.vugt at canonical.com
Tue Jul 16 01:39:04 UTC 2013
My main desktop is indeed raring. However it is significantly
outnumbered by the number of saucy machines I have. I like raring
because it is my fastest build machine by far. So keeps me more productive.
I'm not going to try to justify compiler compatibility any more other
than saying it's a good thing for any project.
The gmock issues just look like CMake magic. So fixable, but not a priority.
On 16/07/13 01:37, Oliver Ries wrote:
> Hi Daniel,
> thanks for pointing this out. Can you help me understand the impact a
> bit better?
> On Sun, Jul 14, 2013 at 9:31 PM, Daniel van Vugt
> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
> It finally happened. lp:mir now depends on C++11 features and
> external packages (google-mock) too heavily to be buildable on
> raring any more.
> Essentially the main problem is that raring uses gcc-4.7 and Mir's
> code depends on more complete C++11 features that only work in
> gcc-4.8. The other issue is that Mir now depends on saucy-specific
> hacks in the google-mock package, which can't be found elsewhere.
> This is a little disappointing. If anyone would like to take on the
> project of making the Mir source more backward compatible, then feel
> free. But maintaining compatibility with raring has now taken up too
> much of my time...
> Looking at your initial mail, the main motivator for offering to support
> Raring was that your own development environment is not on saucy yet
> (though it should;). From this mail I take that gcc 4.8 and gmock test
> are not available on R but became a requirement.
> Is there any other benefit that we can think of that is currently being
> impacted by this incompatibility with R?
More information about the Mir-devel