I think I'd like to handle platform discovery a slightly different way; at the moment, MirPlatformPackage contains enough data to be a unique signature in itself.
The drivers are android.so, mesa.so, etc because they're in the client-platform/ directory. Their full name looks like client-platform/mesa.so, client-platform/android.so, etc.
I think client-platform/client-platform-mesa.so, etc look a bit silly :)
@Cemil - tested, and passed, under sbuild.
I think I'd like to handle platform discovery a slightly different way; at the moment, MirPlatformPackage contains enough data to be a unique signature in itself.
The drivers are android.so, mesa.so, etc because they're in the client-platform/ directory. Their full name looks like client- platform/ mesa.so, client- platform/ android. so, etc.
I think client- platform/ client- platform- mesa.so, etc look a bit silly :)