Commen=
t # 14
on bug 98964<=
/a>
from Emil Velikov
(In reply to Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi from comment #12)
> (In reply to Emil Velikov from comment #11)
> > Above all: yes using hard links is nasty.
>=20
> Thanks for confirming. :-)
>=20
> > If you're having a single (or multiple fixed) GPU system then bui=
lding
> > multiple drivers is a _very_ bad idea. If you're doing that for e=
mbedded
> > systems then it gets even worse. Thus having separate $driver sub=
packages
> > makes no sense :-(
>=20
> I never said it is the same machine all across the board. All of them =
are
> single GPU ones, but historically we have systems with:
> AMD RS780
> NVIDIA (ION1, ION2 and some third one, for our workload, Nouveau is en=
ough)
> AMD Kabini
> AMD Kaveri
> Intel D525
> Most recently Intel J1900
>=20
> The same OS must run on all of them, so it does make sense to build
> different drivers into Mesa but it was also a necessity to save space =
where
> we can. Hence the symlink solution. Custom made OS based on Yocto.
>
If it's an embedded solution you'd want to optimise for the particular
hardware. Namely - compiler optimisations, slimmed down kernel, small drive=
rs,
static linking, LTO etc.=20
Sounds like you're aiming at embedded while doing things like a normal dist=
ro
(barring that those actually ship all the drivers in one package).
> Even if the hardlinks are used, bitbake in Yocto=
has a separate packaging
> stage after "make install" that copies files instead of movi=
ng them so even
> a single subpackage containing all drivers would end up with broken
> hardlinks, thus requiring multiples of what is needed solely for the
> gallium_dri.so and mesa_dri_drivers.so megadrivers.
Sounds like Yocto is broken (like many distros were). Lookup on cp's
--preserve=3D options.
I fear I dealt more than enough off-topic. If you're interested in more pok=
e me
privately or via the mesa-dev mailing list.