Currently, mergin rav1e installs mainly the rav1e binary. Can you extend the ebuild to build the C-API as well? Reproducible: Always Steps to Reproduce: 1. Merge rav1e.
Created attachment 615164 [details] cargo-c-0.5.2.ebuild Here is a quick and dirty cargo-c ebuild.
Created attachment 615166 [details] rav1e-9999.ebuild And here is the even more quick and dirty rav1e ebuild that uses it. Anyway, it works... Interestingly, cargo cinstall seems not to respect the prefix and lib path in the pkg file.
(Also installable in my overlay [1]. Use with caution.) [1] https://gitweb.gentoo.org/repo/user/gerislay.git/commit/?id=1c8e74299a61fa9c4c4b9de368d45681374531d8
Also, my ebuilds do not work with 32 bit. Assuming that the C API is mostly used by ffmpeg, it is not uncommon to need a 32 bit rav1e.
media-libs/libavif ( https://bugs.gentoo.org/711022 ) will also use rav1e C API when available.
I added an ebuild for the new cargo-c and updated the -9999 ebuild to provide optionally the C api. Sorry for the delay but this issue got chewed by my mailbox till today.
Thank you. Do you consider adding a 32-bit build as well? As said, especially ffmpeg (together with installing wine) will need this. Should I open a seperate bug for this?
Of course 32-bit means "installing 32-bit binaries on a 64-bit system". I guess, the correct term is multilib support.
