keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
9ee27a61ca
rpm-ostree/rust/libdnf-sys/Cargo.toml

36 lines
721 B
TOML
Raw Normal View History

rust: move libdnf-sys module to its own crate This is just a cleaner arrangement to make the separation more explicit. It also matches what most other wrapper crates do. One advantage of this is that we can tell cbindgen directly that we don't want it to ever export symbols from `libdnf-sys`. Related discussions in: https://github.com/coreos/rpm-ostree/pull/2047
2020-04-07 18:09:17 +03:00
[package]
name = "libdnf-sys"
version = "0.1.0"
authors = ["Colin Walters <walters@verbum.org>", "Jonathan Lebon <jonathan@jlebon.com>"]
edition = "2018"
Move libdnf build over to Cargo This is now further migration towards Cargo/Rust possible because we switched our main binary. We've had an internal `libdnf-sys` crate for a while, but now it can take over the build of the underlying library too (like many `-sys` crates support). This itself is just an incremental step towards migrating the main rpm-ostree build system to e.g. cmake too (or perhaps directly with the `cc` crate, not sure yet) and driving it via `cargo` too.
2021-01-29 22:47:48 +03:00
links = "dnf"
rust: move libdnf-sys module to its own crate This is just a cleaner arrangement to make the separation more explicit. It also matches what most other wrapper crates do. One advantage of this is that we can tell cbindgen directly that we don't want it to ever export symbols from `libdnf-sys`. Related discussions in: https://github.com/coreos/rpm-ostree/pull/2047
2020-04-07 18:09:17 +03:00
[dependencies]
build(deps): bump cxx from 1.0.30 to 1.0.32 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.30 to 1.0.32. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.30...1.0.32) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-17 03:31:31 +03:00
cxx = "1.0.32"
Introduce CxxGObjectArray, use in lockfile code cxx-rs only supports a few basic types in `Vec<T>`/`CxxVector<T>` and we need to pass an array of GObjects in a few cases. Add a wrapper class hack instead of using `u64` so we at least have some basic safety here and have a convenient place to grep for later when we want to improve this.
2021-03-02 21:20:22 +03:00
glib = "0.10.3"
rust: move libdnf-sys module to its own crate This is just a cleaner arrangement to make the separation more explicit. It also matches what most other wrapper crates do. One advantage of this is that we can tell cbindgen directly that we don't want it to ever export symbols from `libdnf-sys`. Related discussions in: https://github.com/coreos/rpm-ostree/pull/2047
2020-04-07 18:09:17 +03:00
[lib]
name = "libdnf_sys"
path = "lib.rs"
build-sys: Explicit workspace, move libdnf deps to crate First explicitly state that we're a workspace. AIUI this is actually implicit today via our use of a `path` dependency, but in the future we may have other sub-crates. So let's make it explicit now. Also move the libdnf dependencies directly to that sub-crate.
2021-02-02 02:33:55 +03:00
[build-dependencies]
Move libdnf build over to Cargo This is now further migration towards Cargo/Rust possible because we switched our main binary. We've had an internal `libdnf-sys` crate for a while, but now it can take over the build of the underlying library too (like many `-sys` crates support). This itself is just an incremental step towards migrating the main rpm-ostree build system to e.g. cmake too (or perhaps directly with the `cc` crate, not sure yet) and driving it via `cargo` too.
2021-01-29 22:47:48 +03:00
cmake = "0.1.45"
build(deps): bump system-deps from 2.0.3 to 3.0.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v2.0.3...v3.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-18 02:21:53 +03:00
system-deps = "3.0"
build-sys: Explicit workspace, move libdnf deps to crate First explicitly state that we're a workspace. AIUI this is actually implicit today via our use of a `path` dependency, but in the future we may have other sub-crates. So let's make it explicit now. Also move the libdnf dependencies directly to that sub-crate.
2021-02-02 02:33:55 +03:00
anyhow = "1.0"
build(deps): bump cxx-build from 1.0.31 to 1.0.32 Bumps [cxx-build](https://github.com/dtolnay/cxx) from 1.0.31 to 1.0.32. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.31...1.0.32) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-19 20:55:43 +03:00
cxx-build = "1.0.32"
build-sys: Explicit workspace, move libdnf deps to crate First explicitly state that we're a workspace. AIUI this is actually implicit today via our use of a `path` dependency, but in the future we may have other sub-crates. So let's make it explicit now. Also move the libdnf dependencies directly to that sub-crate.
2021-02-02 02:33:55 +03:00
# This currently needs to duplicate the libraries from libdnf
[package.metadata.system-deps]
rpm = "4"
# libdnf dependencies
librepo = "1"
libsolv = "0.7"
libsolvext = "0.7"
gpgme = "1"
openssl = "1"
libcurl = "7"
sqlite3 = "3"
modulemd = { name = "modulemd-2.0", version = "2" }
jsonc = { name = "json-c", version = "0" }
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
glib = { name = "glib-2.0", version = "2" }
Reference in New Issue Copy Permalink