[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Naming of native-inputs/inputs/propagated-inputs
From: |
Ben Sturmfels |
Subject: |
Re: Naming of native-inputs/inputs/propagated-inputs |
Date: |
Tue, 23 Jul 2019 20:36:00 +1000 |
User-agent: |
mu4e 1.2.0; emacs 26.2 |
On Tue, 23 Jul 2019, Ricardo Wurmus wrote:
> The difference between “native-inputs” and “inputs” is not about whether
> they are needed at build time or runtime. The difference only really
> comes into play when cross-building. “native-inputs” must be of the
> host architecture, while “inputs” are for the target architecture.
>
> It is correct that “native-inputs” often happen to be only used during
> the build, but that doesn’t need to be the case.
>
> Ultimately, runtime inputs are determined by whether they are referenced
> in the output. This is orthogonal to whether they are listed in the
> “native-inputs”, “inputs”, or even “propagated-inputs” field.
Thanks for the clarification Ricardo!
Regards,
Ben
signature.asc
Description: PGP signature