Skip to content

Commit a52ce18

Browse files
shr-projectrpurdie
authored andcommitted
cargo.bbclass: show PACKAGECONFIG_CONFARGS in bbnote
* PACKAGECONFIG_CONFARGS was added in: https://git.openembedded.org/openembedded-core/commit/?id=16745b20452de60ae2474433cc1a2fb1ed9f6a64 but it wasn't added in bbnote above which might lead to confusing errors like I got now: NOTE: cargo build -v --frozen --target aarch64-webos-linux-gnu --release --manifest-path=.../git//Cargo.toml error: unexpected argument '--cfg' found Usage: cargo build --verbose... --frozen --target [<TRIPLE>] --release --manifest-path <PATH> and was wondering where --cfg came from. * it was from recipe where we already use: RUSTFLAGS:append = " ${PACKAGECONFIG_CONFARGS}" it will be difficult to use PACKAGECONFIG for RUSTFLAGS and prevent them to be used here for cargo as well, what about the recipes which need them to explicitly append them to CARGO_BUILD_FLAGS ? Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1 parent 6c06022 commit a52ce18

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

meta/classes-recipe/cargo.bbclass

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ oe_cargo_build () {
4747
export RUSTFLAGS="${RUSTFLAGS}"
4848
bbnote "Using rust targets from ${RUST_TARGET_PATH}"
4949
bbnote "cargo = $(which ${CARGO})"
50-
bbnote "${CARGO} build ${CARGO_BUILD_FLAGS} $@"
50+
bbnote "${CARGO} build ${CARGO_BUILD_FLAGS} ${PACKAGECONFIG_CONFARGS} $@"
5151
"${CARGO}" build ${CARGO_BUILD_FLAGS} ${PACKAGECONFIG_CONFARGS} "$@"
5252
}
5353

0 commit comments

Comments
 (0)