On Mon, Jul 22, 2024 at 02:34:28PM +1000, Jonathan Gray wrote:
> On Sat, Jul 13, 2024 at 12:51:39PM +0200, Rafael Sadowski wrote:
> > OK to import intel-media-driver-24.1.5? Keep in mind, to build this you
> > need libv installed from xenocara.
> > 
> > Comment:
> > Intel(R) Media Driver for VAAPI
> > 
> > Description:
> > VA-API (Video Acceleration API) user mode driver for Intel GEN Graphics family
> > 
> > VA-API is an open-source library and API specification, which provides access to
> > graphics hardware acceleration capabilities for video processing. It consists of
> > a main library and driver-specific acceleration backends for each supported
> > hardware vendor.
> > 
> > The current video driver backend provides a bridge to the GEN GPUs through the
> > packaging of buffers and commands to be sent to the i915 driver for exercising
> > both hardware and shader functionality for video decode, encode, and processing.
> 
> Why are you putting .so files into X11BASE with @sample?
> 
> lib/xorg/
> lib/xorg/modules/
> @so lib/xorg/modules/iHD_drv_video.so
> @sample ${X11BASE}/lib/modules/drivers/iHD_drv_video.so
> 
> @sample is for sample configuration files according to pkg_create(1)
> 
> Shouldn't the .so built in ports go into LOCALBASE and
> libva search both X11BASE and LOCALBASE paths?
> 

In Prague we discussed this a bit. In the past there have been some
resitance against having stuff from xenocara reach out to the ports
tree.

But I tend to agree that it wold be cleander to add LOCALBASE/lib/dri
to the search path of libva (and more generally Mesa/Xserver too) to
help with this kind of situation.

-- 
Matthieu Herrb