unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Difference between search-paths and native-search-path
Date: Sat, 26 Aug 2017 11:20:16 +0200	[thread overview]
Message-ID: <0a1c045c-4c4b-ba05-b6fd-9994a741e859@crazy-compilers.com> (raw)
In-Reply-To: <87d17kvzt9.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Am 25.08.2017 um 10:04 schrieb Ricardo Wurmus:
>> what is  the difference between search-paths and native-search-path? The
>> manual describes search-paths at [1], but native-search-paths are only
>> named at [2] without any description.
> “native-search-paths” are used when cross-building.  The arm eabi
> cross-compiler, for example, declares CROSS_C_INCLUDE_PATH and
> CROSS_LIBRARY_PATH as a native search path, because these are needed
> when cross-building applications for the arm eabi target.

Thanks. Does this mean:

- native-search-paths are set when building a packages, They are
constructed based on the native-inputs only.

- search-paths are set when installing a package, based on all inputs.
These paths are *not* available then builiding the package.

Is this correct?

What happens if $KLM_PATH is defined as "native-search-path" by package
A and defined as "search-path" by package B?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |


[-- Attachment #2: Type: text/html, Size: 1843 bytes --]

      reply	other threads:[~2017-08-26  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  7:14 Difference between search-paths and native-search-path Hartmut Goebel
2017-08-25  8:04 ` Ricardo Wurmus
2017-08-26  9:20   ` Hartmut Goebel [this message]

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=0a1c045c-4c4b-ba05-b6fd-9994a741e859@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).