Re: Prevent native-inputs references ending up in the final binary

[Tobias Geerinckx-Rice <me@tobias.gr>]

Hullo,

On Fri, 2018-01-26 at 00:56 +0000, Fis Trivial wrote:
> On 01/20/2018 06:40 PM, Danny Milosavljevic wrote:
> > I think that native-inputs shouldn't end up in the final binary as
> > a
> > reference, especially when cross-compiling
> > (but we don't do cross-compilation much in Guix - usually, we let
> > qemu-arm emulate the ARM CPU on x86_64 and just call the target
> > tool :) ).
> > 
> > If there are indeed parts of the same package, one a native part
> > and one a
> > runtime dependency part, I actually write the same package
> > reference twice,
> > once in the inputs, once in the native-inputs, in my custom package
> > definitions.
> > 
> > In a "previous life" I did a lot of Linux cellphone development
> > and,
> > there, it was kinda important that a x86_64 toolchain doesn't end
> > up being referenced in an ARM binary, so the habit stuck - and I
> > think it's important to distinguish the mold used to form a product
> > from an integral part of that product.
> > 
> 
> I'm no expert, but can this little utility from nix help?
> https://nixos.org/patchelf.html

In what way?

Patchelf re-writes library and/or loader paths in compiled binaries.
It's cool, but I don't immediately see the connexion...

Kind regards,

T G-R