From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] vdpau and vdpauinfo
Date: Mon, 28 Dec 2015 19:04:11 -0500 [thread overview]
Message-ID: <20151229000411.GA3825@jasmine> (raw)
In-Reply-To: <20151228230102.GA15315@debian.fritz.box>
On Tue, Dec 29, 2015 at 12:01:02AM +0100, Andreas Enge wrote:
> 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.
Sorry, I meant to write inputs.
>
> > 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.
Okay, I'll try that.
>
> Andreas
>
next prev parent reply other threads:[~2015-12-29 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 14:45 [PATCH 0/2] vdpau and vdpauinfo Efraim Flashner
2015-12-21 14:45 ` [PATCH 1/2] gnu: Add libvdpau Efraim Flashner
2015-12-21 14:45 ` [PATCH 2/2] gnu: Add vdpauinfo Efraim Flashner
2015-12-26 5:51 ` [PATCH 0/2] vdpau and vdpauinfo Leo Famulari
2015-12-26 20:27 ` Efraim Flashner
2015-12-28 19:59 ` Leo Famulari
2015-12-28 23:01 ` Andreas Enge
2015-12-29 0:04 ` Leo Famulari [this message]
2015-12-29 2:40 ` Leo Famulari
2015-12-29 12:14 ` Efraim Flashner
2015-12-31 10:44 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151229000411.GA3825@jasmine \
--to=leo@famulari.name \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.