From: Peter Polidoro <peter@polidoro.io>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: Finding Dependencies at Run Time
Date: Wed, 13 Jul 2022 13:47:45 -0400 [thread overview]
Message-ID: <86bktshp6m.fsf@polidoro.io> (raw)
In-Reply-To: <24DD9713-A088-4C6A-8D8B-5DCF60E623AF@lepiller.eu>
> The mecanism depends a bit on the build system but for C
> programs, it's embeded at build-time in its RPATH. For
> applications, there are
> wrappers
> (https://guix.gnu.org/manual/devel/en/html_node/Build-Utilities.html#Wrappers).
So in general, packages use environment variables to find the
absolute paths of their dependencies in the store?
In a package definition, are those dependency paths always set
using wrap-program? Are search-paths, native-search-paths, and
setenv also used to set those environment variables or are those
used for something else?
> Otherwise, we have to propagate run-time dependencies.
So how else can packages propagate run-time dependencies besides
environment variables?
next prev parent reply other threads:[~2022-07-13 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:56 Finding Dependencies at Run Time Peter Polidoro
2022-07-13 16:03 ` Julien Lepiller
2022-07-13 17:47 ` Peter Polidoro [this message]
2022-07-13 18:39 ` Julien Lepiller
2022-07-13 18:51 ` Peter Polidoro
2022-07-13 21:02 ` Julien Lepiller
2022-07-14 17:47 ` Peter Polidoro
2022-07-16 21:53 ` Thiago Jung Bauermann
2022-07-14 8:25 ` Ricardo Wurmus
2022-07-14 8:48 ` Philip McGrath
2022-07-14 11:28 ` Ricardo Wurmus
2022-07-14 13:27 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bktshp6m.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).