> Something else scares me actually. Although the reality hasn't changed, it's
> now more clear that any ABI bump to libmircommon or libmirplatform will break
> 3rd party graphics drivers.
>
The android platform depends-on the android drivers (so we can't break the android drivers with our abi/api changes).
The mesa platform provides its native window type and some function hooks that are needed to the mesa drivers, so the drivers depend-on the platform, and abi changes could break the drivers.
I guess the long term solution is to pull parts of the mesa drivers into the mesa platform, and have mesa depend-on headers provided by the drivers.
> Something else scares me actually. Although the reality hasn't changed, it's
> now more clear that any ABI bump to libmircommon or libmirplatform will break
> 3rd party graphics drivers.
>
The android platform depends-on the android drivers (so we can't break the android drivers with our abi/api changes).
The mesa platform provides its native window type and some function hooks that are needed to the mesa drivers, so the drivers depend-on the platform, and abi changes could break the drivers.
I guess the long term solution is to pull parts of the mesa drivers into the mesa platform, and have mesa depend-on headers provided by the drivers.