rpm-ostree/ci/install-extra-builddeps.sh

#!/usr/bin/env bash
# cxx.rs (cxxbridge) isn't packaged in Fedora today.  Both it and cbindgen generate
# source code, which we vendor along with our dependent crates into release
# tarballs.  Note in the future it's likely we stop using cbindgen entirely in
# favor of cxx.rs.

set -euo pipefail

CXX_VER=$(cargo metadata --format-version 1 | jq -r '.packages[]|select(.name == "cxx").version')
cargo install cxxbridge-cmd --version "${CXX_VER}"

CBINDGEN_VER=$(cargo metadata --format-version 1 | jq -r '.packages[]|select(.name == "cbindgen").version')
cargo install cbindgen --version "${CBINDGEN_VER}"
ci: fix install-extra logic This fixes `install-extra-builddeps.sh` helper, by letting cargo detect whether the target binary is already present in the environment with the expected version. This is in order to avoid mismatches in generated code when the library version is bumped, and stale binaries are present on the system. 2021-01-25 17:04:35 +03:00			`#!/usr/bin/env bash`
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build. 2020-12-31 19:55:19 +03:00			`# cxx.rs (cxxbridge) isn't packaged in Fedora today. Both it and cbindgen generate`
			`# source code, which we vendor along with our dependent crates into release`
			`# tarballs. Note in the future it's likely we stop using cbindgen entirely in`
			`# favor of cxx.rs.`
ci: fix install-extra logic This fixes `install-extra-builddeps.sh` helper, by letting cargo detect whether the target binary is already present in the environment with the expected version. This is in order to avoid mismatches in generated code when the library version is bumped, and stale binaries are present on the system. 2021-01-25 17:04:35 +03:00
			`set -euo pipefail`

			`CXX_VER=$(cargo metadata --format-version 1 \| jq -r '.packages[]\|select(.name == "cxx").version')`
			`cargo install cxxbridge-cmd --version "${CXX_VER}"`

			`CBINDGEN_VER=$(cargo metadata --format-version 1 \| jq -r '.packages[]\|select(.name == "cbindgen").version')`
			`cargo install cbindgen --version "${CBINDGEN_VER}"`