[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] vdpau and vdpauinfo
From: |
Andreas Enge |
Subject: |
Re: [PATCH 0/2] vdpau and vdpauinfo |
Date: |
Tue, 29 Dec 2015 00:01:02 +0100 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Mon, Dec 28, 2015 at 02:59:29PM -0500, Leo Famulari wrote:
> I think they would be native-inputs for vlc, mplayer, and mpv, because
> those programs are written (mostly) in C and C++, and so we can provide
> the path to the store directory at compile-time.
No, they should be normal inputs - they should be compiled for the target
architecture where the binary is supposed to be run. The binaries themselves
will link dynamically to the libraries.
> I added libvdpau as a native-input to each and they build, but I don't
> know how to test if the compilation is using libvdpau and using it
> correctly.
You could search for it in the build log, in particular during the configure
phase. And you could run "ldd" on the resulting binary and check whether
the libraries appear.
Andreas
- [PATCH 0/2] vdpau and vdpauinfo, Efraim Flashner, 2015/12/21
- [PATCH 1/2] gnu: Add libvdpau., Efraim Flashner, 2015/12/21
- [PATCH 2/2] gnu: Add vdpauinfo., Efraim Flashner, 2015/12/21
- Re: [PATCH 0/2] vdpau and vdpauinfo, Leo Famulari, 2015/12/26
- Re: [PATCH 0/2] vdpau and vdpauinfo, Efraim Flashner, 2015/12/26
- Re: [PATCH 0/2] vdpau and vdpauinfo, Leo Famulari, 2015/12/28
- Re: [PATCH 0/2] vdpau and vdpauinfo,
Andreas Enge <=
- Re: [PATCH 0/2] vdpau and vdpauinfo, Leo Famulari, 2015/12/28
- Re: [PATCH 0/2] vdpau and vdpauinfo, Leo Famulari, 2015/12/28
- Re: [PATCH 0/2] vdpau and vdpauinfo, Efraim Flashner, 2015/12/29
- Re: [PATCH 0/2] vdpau and vdpauinfo, Efraim Flashner, 2015/12/31