emit inline checksum

[ensc]

recent OE requires valid checksums for crates://. Patch adds them as something like

    crate://crates.io/addr2line/0.21.0;sha256sum=8a30b2e23b9e17a9f90641c7ab1549cd9b44f296d3ccbf309d2863cfe398a0cb;addr2line-0.21.0.sha256sum=8a30b2e23b9e17a9f90641c7ab1549cd9b44f296d3ccbf309d2863cfe398a0cb \

Due to restrictions in bitbake, a simple sha256sum=... does not suffice but it must be expressed with the crate name (<name>-<version>.sha256sum). Simple argument is kept for completeness.

[Finomnis]

@kraj Bump

[Finomnis]

@kraj Is this crate still maintained? It does no longer produce compilable recipes for newer Yocto Versions. This PR fixes it.

[kraj]

Yes it is

[Finomnis]

Yes it is

In that case, I apologize for my rudeness.

Either way, I'd love to get this merged and released :)

[IniterWorker]

I've been following the work of @jaskij, @kkettinger and @ensc closely, and I'm inclined to suggest adopting an approach similar to what's available in this file.

@codyps and @ColinFinck, I'm willing to offer my assistance in maintaining this repository cargo-bitbake.

[jaskij]

@IniterWorker you credit me needlessly, I just incorporated this change into my version because I needed both.

[Finomnis]

Any news here? This is becoming a problem due to its incompatibility with newer Yocto versions ...

Some further discussion about this was done in #75, but whatever way works is fine for me, I just need this for a Yocto project :/

[jaskij]

I have been meaning to do a ground-up rewrite of the project, since it has other issues and it shouldn't be hard, but I'm not currently working with anything Yocto, so it's been put on hold.

Is there something missing in #75 which means you can't just use that version? You can always use that version by running

cargo install --git https://github.com/jaskij/cargo-bitbake.git

[Finomnis]

Yah, that's what I've been doing, but it seems kinda hacky for production use

[Finomnis]

@jaskij If you do a ground-up rework, there's a couple of features that would be absolutely amazing and are making my life very difficult right now:

• Proper integration of Rust's dependencies into Yocto SBOM
• Proper entries of dependencies and dependency licenses in tmp/deploy/licenses
• Proper license check through INCOMPATIBLE_LICENSE

Although I'm not sure how many of those can be accomplished with cargo-bitbake and which of those features must be integrated into the official yocto rust layer.

[jaskij]

Yah, that's what I've been doing, but it seems kinda hacky for production use

Those are still files where you manually run the generator and add the output to git, so it's not that bad IMO