From: "yarl baudig" <yarl-baudig@mailoo.org>
To: ludo@gnu.org
Cc: 59843@debbugs.gnu.org
Subject: [bug#59843] [PATCH] shell: Enable --target for guix shell (--development)
Date: Wed, 14 Dec 2022 21:57:37 +0100 (CET) [thread overview]
Message-ID: <ea-mime-639a38c1-55fa-721b84fa@www.mailo.com> (raw)
In-Reply-To: <87o7s6tfn0.fsf@gnu.org>
I responded too fast. You are right, something is wrong. Not every path is accessible. I will try to understand when I'll have some time.
---- Message d'origine ----
> De : Ludovic Courtès <ludo@gnu.org>
> À : Yarl Baudig <yarl-baudig@mailoo.org>
> Sujet : Re: bug#59843: [PATCH] shell: Enable --target for guix shell (--development)
> Date : 14/12/2022 11:59:31 Europe/Paris
> Copie à : 59843@debbugs.gnu.org
>
> Hi,
>
> Yarl Baudig <yarl-baudig@mailoo.org> skribis:
>
> > This enable the use of --target for development inputs, that is:
> > with `guix shell`, includes the dependencies for cross-building packages
> > given with --development
> >
> > * guix/scripts/environment.scm: Enable --target.
> > * guix/scripts/shell.scm: Enable --target.
> > * doc/guix.texi: Document it.
>
> This change won’t give something useful per se, because the environment
> will contain a mixture of “host” and “build” inputs.
>
> To make it work, we need two profiles: one for “build” inputs, and one
> for “host/target” inputs. Search path environment variables must be
> evaluated in a way that accounts for these two profiles. For example,
> target libraries will appear on CROSS_C_INCLUDE_PATH but not on
> C_INCLUDE_PATH.
>
> Does that make sense?
>
> IOW, it’s a trickier endeavor that one could hope for. :-)
>
> Thanks,
> Ludo’.
>
next prev parent reply other threads:[~2022-12-14 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 20:30 [bug#59843] [PATCH] shell: Enable --target for guix shell (--development) Yarl Baudig
2022-12-14 10:59 ` Ludovic Courtès
2022-12-14 16:26 ` yarl baudig
2022-12-14 20:57 ` yarl baudig [this message]
2022-12-21 13:42 ` bug#59843: " Ludovic Courtès
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=ea-mime-639a38c1-55fa-721b84fa@www.mailo.com \
--to=yarl-baudig@mailoo.org \
--cc=59843@debbugs.gnu.org \
--cc=ludo@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.