https://bugs.freedesktop.org/show_bug.cgi?id=80615
--- Comment #6 from Alexandre Demers <alexandre.f.dem...@gmail.com> ---
Christian, could you give us your input on this issue and proposed fix?
(In reply to comment #5)
> AFAICS the whole thing is quite inconsistent.
>
> (In reply to comment #3)
> > That's something I hadn't noticed. However, it still bugs me. Why would this
> > component deal with its installation path differently from the others. Let's
> > have a look at opencl, vdpau and egl :
> > --with-vdpau-libdir=DIR directory for the VDPAU libraries
> > [default=${libdir}/vdpau]
> Defined by libvdpau. Can be accessed/queried via pkg-config (moduledir)
>
> > --with-opencl-libdir=DIR
> > directory for auxiliary libraries used by the
> > OpenCL
> > implementation [default=${libdir}/opencl]
> Unused.
>
> > --with-egl-driver-dir=DIR
> > directory for EGL drivers
> > [[default=${libdir}/egl]]
> >
> Internal to mesa. Ideally we'll have this one nuked for the next release.
>
> > And then we have omx :
> > --with-omx-libdir=DIR directory for the OMX libraries
> >
> Defined by bellagio. Can be accessed/queried via pkg-config (pluginsdir)
>
> > It seems omx is one of a kind by not using something ${libdir}/bellagio. By
> > doing this small modification, a user wouldn't be surprise to have this only
> > component install not in the libdir he asked for, but he would still be able
> > to set a different path if needed.
> >
> It can be argued either way, yet imho we should be using pkg-config when
> possible. I don't mind either way, as long as Christian is happy with the
> solution.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
