On Wed, 13 May 2026 at 14:03, Nirbheek Chauhan <[email protected]> wrote:
> Yes, this means each plugin has its own copy of gtk-rs, gstreamer-rs, > and other common crates. The reasons for this are complicated: > > https://viruta.org/rust-stable-abi.html#rust_does_not_have_a_stable_abi > > If you see the librsvg recipe, it does the same thing. Tarun is going > to change these git repo URLs to also use crates.io links in V3. Are these copies listed in Cargo.toml of the plugins? If so, they shouldn't be manually specified in SRC_URI, instead they should be in the auto-generated gstreamer1.0-plugins-rs-crates.inc, and the build process should be able find and use them. There are concerns over discovering and fixing a critical security issue in one of the components, when they are vendored into the source tree this way, all because the compiler team can't settle on an ABI. I'm sure you've seen that many times before. The issue is general to rust (or node.js or any number of similar approaches to dependency management) and not gstreamer-specific, but I still wanted to mention it. The problem is, when it happens, it's the integrators that have to deal with it, not the compiler writers and not the component writers. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#236966): https://lists.openembedded.org/g/openembedded-core/message/236966 Mute This Topic: https://lists.openembedded.org/mt/119293604/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
