Ragnar Thomsen wrote:
On Thursday 10 July 2014 16:39:17 Bruce Dubbs wrote:
I finally got around to this and it worked fine.  Thanks Ragnar.

Now, how to add it to the book?  AFAICT, there is only the github
version.  I can download a .zip file from there, but I'm sure the md5sum
will change.  I can create a tar.xz version on anduin easily enough.
The last change was
It uses cmake -- the only driver for xorg that does.  Probably not a big
deal.  But it seems to want to install in /usr/local even if
-DCMAKE_INSTALL_PREFIX=/opt/xorg is specified.  I can investigate that
later.  It only installs libvdpau_va_gl.so{,.1} anyway so a simple cp
would work for that.

mkdir build
cd build
cmake ..
make
make check
cp -av libvdpau_va_gl $XORG_PREFIX/lib/vdpau/

I install in /usr, and -DCMAKE_INSTALL_PREFIX=/usr works fine for me.

Right. -DCMAKE_INSTALL_PREFIX=$XORG_PREFIX works for those who don't install in /usr.

There are two issues:

1.  Where to put it?  I can just add it to the libvdpau section or I can
create a separate section.  I lean toward the libvdpau section.

Well, it is a backend for vdpau, so I would put it in video acceleration
section.

Yes, but as a separate page or combined with libvdpau? Since we already combine libva-intel-driver with libva, I'll combine libvdpau_va_gl with libvdpau.

2.  Should I create a separate tarball?  The last change was June 17, so
it is being updated.  I lean toward just presenting the url and adding a
note about changing md5sums.

There are releases on the github page (click on releases button). The latest
one being:
https://github.com/i-rinat/libvdpau-va-gl/archive/v0.3.4.tar.gz

Almost perfect. The file name is weird in that it doesn't have the package name as a part of the file name, but it expands to the libvdpau-va-gl-0.3.4 directory. I'll note that.

I'll go ahead and update this later today with libvdpau-0.8.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to