@@ -11,10 +11,6 @@
inherit cargo_common pkgconfig
-# the binaries we will use
-CARGO_C_BUILD = "cargo-cbuild"
-CARGO_C_INSTALL = "cargo-cinstall"
-
# We need cargo-c to compile for the target
BASEDEPENDS:append = " cargo-c-native"
@@ -25,16 +21,13 @@ cargo_c_do_compile() {
oe_cargo_fix_env
export RUSTFLAGS="${RUSTFLAGS}"
bbnote "Using rust targets from ${RUST_TARGET_PATH}"
- bbnote "cargo-cbuild = $(which ${CARGO_C_BUILD})"
- bbnote "${CARGO_C_BUILD} cbuild ${CARGO_BUILD_FLAGS}"
- "${CARGO_C_BUILD}" cbuild ${CARGO_BUILD_FLAGS}
+ cargo-cbuild cbuild ${CARGO_BUILD_FLAGS}
}
cargo_c_do_install() {
oe_cargo_fix_env
export RUSTFLAGS="${RUSTFLAGS}"
- bbnote "cargo-cinstall = $(which ${CARGO_C_INSTALL})"
- "${CARGO_C_INSTALL}" cinstall ${CARGO_BUILD_FLAGS} \
+ cargo-cinstall cinstall ${CARGO_BUILD_FLAGS} \
--destdir ${D} \
--prefix ${prefix} \
--libdir ${libdir} \
There's no point in having variables to control what cargo-c binaries are executed as there are no alternatives. The cargo class does this because it is used when bootstrapping cargo. This isn't needed to build cargo-c, but the pattern was copied into this class. Signed-off-by: Ross Burton <ross.burton@arm.com> --- meta/classes-recipe/cargo_c.bbclass | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-)