Autopilot controvercy, the continuatron!

Christopher James Halse Rogers chris at cooperteam.net
Wed Sep 10 05:30:24 UTC 2014


So, having implemented the controversial surface-to-screen interface 
for autopilot, it's now also a controversial merge proposal!

https://code.launchpad.net/~raof/mir/the-least-dirty-thing/+merge/231679

The question is “should we have the debugging interface provided by a 
separate libmirclient-debug-extension library or as a part of the core 
libmirclient?”

The source of contention is that libmirclient-debug-extension is quite 
large - about as big as libmirclient itself - because the current 
implementation of libmirclient means it must duplicate a lot of code 
already in libmirclient.so.

I think that the benefits of having it in its own library - it's 
obvious when you're doing debug things, it's obvious that changing 
behaviour doesn't break the core client ABI, etc - outweigh the 300K of 
extra disc space required. Particularly since this library won't be 
installed on the production images; it'll be installed as a part of 
setting up the autopilot tests.

What do the other people who haven't weighed in on this MP think?

Chris




More information about the Mir-devel mailing list