mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer-rs.git
synced 2024-12-02 06:21:06 +00:00
782d84bede
The `links` annotation in `Cargo.toml` is intended to ensure that in the crate graph there's at most one crate that's an implementation of some sort concept. This can make sense in some scenarios, most prominent of which is when the crate defines `#[no_mangle]` symbols (e.g. by compiling a vendored C library.) In that situation linking a binary that depends on two versions of the library cannot work because of colliding symbol names. There does not appear to be a similar reason to impose such a restriction on the users of `gstreamer-sys` and similar, however. All of these crates link to a system library, they do not define any `#[no_mangle]` symbols nor they vendor and build C libraries as part of their build process. All they do is linking to a system library. Most likely all the different versions of the bindings will link to the exact same library too. I haven't seen any global resources that these bindings use to ensure soundness of the library, either.
18 lines
555 B
Rust
18 lines
555 B
Rust
// Generated by gir (https://github.com/gtk-rs/gir @ b193568)
|
|
// from gir-files (https://github.com/gtk-rs/gir-files @ 7d95377)
|
|
// from gst-gir-files (https://gitlab.freedesktop.org/gstreamer/gir-files-rs.git @ 831b444)
|
|
// DO NOT EDIT
|
|
|
|
#[cfg(not(feature = "dox"))]
|
|
use std::process;
|
|
|
|
#[cfg(feature = "dox")]
|
|
fn main() {} // prevent linking libraries to avoid documentation failure
|
|
|
|
#[cfg(not(feature = "dox"))]
|
|
fn main() {
|
|
if let Err(s) = system_deps::Config::new().probe() {
|
|
println!("cargo:warning={}", s);
|
|
process::exit(1);
|
|
}
|
|
}
|