libmirclient exports symbols only needed by the test framework

[Alan Griffiths]

The acceptance tests ought to work through APIs exposed to users of Mir and not use backdoors. (They are about behaviour the users require.)

This is mostly true, but the test framework used for the tests needs access to some otherwise internal symbols of libmirclient vis:

   MirConnection::MirConnection*;
   MirConnection::connect*;
   MirConnection::disconnect*;
   mir::client::DefaultConnectionConfiguration::*;
   vtable?for?mir::client::DefaultConnectionConfiguration;
   typeinfo?for?mir::client::DefaultConnectionConfiguration;

These are to support stubbing the client graphics. (See UsingStubClientPlatform and StubConnectionConfiguration.)

That's a lot of internals exposed that ought to be hidden.

[Chris Halse Rogers (raof)]

I've already got part of a stub client platform in the privatise-all-the-things branch. It should be reasonable to get it usable for all the acceptance tests.

[Daniel van Vugt (vanvugt)]

Oh how nice it would be for our tests to not copy in the individual object files of libmirclient :)

[Michał Sawicz (saviq)]

Syncing task from Mir.