|
From: | Hartmut Goebel |
Subject: | Re: Difference between search-paths and native-search-path |
Date: | Sat, 26 Aug 2017 11:20:16 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
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 | address@hidden | | www.crazy-compilers.com | compilers which you thought are impossible | |
[Prev in Thread] | Current Thread | [Next in Thread] |