Reasons to require platforms to link against libmirplatform

Daniel van Vugt daniel.van.vugt at canonical.com
Wed Sep 23 01:39:38 UTC 2015


As discussed yesterday, I think long term we need to get away from 
requiring drivers to link to anything at all. Because some 
vendors/lawyers require that, and specifically require that they not be 
asked to link to LGPL code. Aiming for this higher goal will also force 
us to think more deeply and build a better system...


On 22/09/15 23:31, Andreas Pokorny wrote:
> Hi again,
>
> After another short round of discussion during standup we came to the
> following conclusion:
>   - provide a library with mir::graphics::* symbols, named
> libmirplatform-graphics.so
>   - reduce libmirplatform to udev::Monitor program::options and related
> utilities, named libmirplatform.so
>   - provide a library with mir::input::* symbols, named
> libmirplatform-input.so
>
> instead of lumping them all together in a single library.
>
> regards,
> Andreas
>
>



More information about the Mir-devel mailing list