Re: [gentoo-dev] [PATCH] cargo.eclass: Add cargo_target_dir helper function

[Florian Schmaus <flow@gentoo.org>]

[-- Attachment #1.1.1: Type: text/plain, Size: 917 bytes --]

On 13/06/2024 17.03, James Le Cuirot wrote:
> Several Cargo-based ebuilds cannot use cargo_src_install for various
> reasons and manually install binaries from within the target directory
> instead. It is common to see `target/$(usex debug debug release)`, but
> this lacks the target ABI when cross-compiling, so provide a helper
> function.

Glad that someone is working on better cross-compilation support for 
rust. :)

That said, many rust ebuilds generate shell completions by invoking the 
just compiled binary in src_install(). This does not work out of the box 
when cross-compiling.

Is there anything we can or should do about it (besides binfmt_misc)? 
For example, asking the according projects to implement a mechanism to 
extract the completions files from the binary without running it, or 
have the build system generate the completion files as result of the build?

- Flow




[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17797 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]