It appears we could safely fix this on lp:mir/0.26 too. Because clients only have direct bindings to libmirclient, and servers don't have direct bindings to libmirplatform or graphics drivers.
You can verify that with:
objdump -x /path/to/binary | grep NEEDED
It appears we could safely fix this on lp:mir/0.26 too. Because clients only have direct bindings to libmirclient, and servers don't have direct bindings to libmirplatform or graphics drivers.
You can verify that with:
objdump -x /path/to/binary | grep NEEDED