Difference between search-paths and native-search-path

Difference between search-paths and native-search-path

[Hartmut Goebel]

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

Hi,

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.

[1]
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-package.html#index-search-paths-1
[2]
https://www.gnu.org/software/guix/manual/html_node/package-Reference.html

-- 
Regards
Hartmut Goebel

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


[-- Attachment #2: 0xBF773B65.asc --]
[-- Type: application/pgp-keys, Size: 14855 bytes --]

Re: Difference between search-paths and native-search-path

[Ricardo Wurmus]

Hi Hartmut,

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

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: Difference between search-paths and native-search-path

[Hartmut Goebel]

[-- 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 --]