Open ensc opened 7 months ago
@kraj Bump
@kraj Is this crate still maintained? It does no longer produce compilable recipes for newer Yocto Versions. This PR fixes it.
Yes it is
Yes it is
In that case, I apologize for my rudeness.
Either way, I'd love to get this merged and released :)
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
.
@IniterWorker you credit me needlessly, I just incorporated this change into my version because I needed both.
Any news here? This is becoming a problem due to its incompatibility with newer Yocto versions ...
Some further discussion about this was done in https://github.com/meta-rust/cargo-bitbake/pull/75, but whatever way works is fine for me, I just need this for a Yocto project :/
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
Yah, that's what I've been doing, but it seems kinda hacky for production use
@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:
tmp/deploy/licenses
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.
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
recent OE requires valid checksums for
crates://
. Patch adds them as something likeDue to restrictions in
bitbake
, a simplesha256sum=...
does not suffice but it must be expressed with the crate name (<name>-<version>.sha256sum
). Simple argument is kept for completeness.