unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, guix-devel@gnu.org
Subject: Re: [DOUBT]: native-search-paths VS search-paths
Date: Tue, 09 Feb 2021 13:26:17 +0100	[thread overview]
Message-ID: <1bd1a30d9c0e2d1c50e2c4402eca291b1999030f.camel@student.tugraz.at> (raw)
In-Reply-To: <80cb9703-154e-36ac-a4e9-ee2da9c9fb97@crazy-compilers.com>

Am Dienstag, den 09.02.2021, 11:22 +0100 schrieb Hartmut Goebel:
> Am 09.02.21 um 11:06 schrieb Leo Prikler:
> > Depends on the package.  If it gets propagated into the build
> > environment, the variable is set as well.  At other times, it might
> > be
> > set through the wrap phase for runtime purposes.
> 
> This makes me think whether the wrap-phase of the qt-build-system
> does 
> it right (even after 45784 is merged): It searches the "inputs" for
> some 
> directories. This has the major drawback of including native-inputs 
> (most notable: cmake).
It probably does some wrong things there.  I'm also not sure if we can
distinguish between inputs and native-inputs at this stage, since IIRC
both get merged into %build-inputs, which is then passed as inputs.

For a similar issue look at python packages built with meson – they
likely retain a reference to meson as well.

Regards,
Leo



  reply	other threads:[~2021-02-09 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  9:32 [DOUBT]: native-search-paths VS search-paths Leo Prikler
2021-02-09  9:56 ` Raghav Gururajan
2021-02-09 10:06   ` Leo Prikler
2021-02-09 10:15     ` Raghav Gururajan
2021-02-09 10:22     ` Hartmut Goebel
2021-02-09 12:26       ` Leo Prikler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-09  8:58 Raghav Gururajan

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=1bd1a30d9c0e2d1c50e2c4402eca291b1999030f.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).