]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
cargo.bbclass: show PACKAGECONFIG_CONFARGS in bbnote
authorMartin Jansa <martin.jansa@gmail.com>
Thu, 20 Mar 2025 16:55:16 +0000 (17:55 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 25 Mar 2025 21:20:05 +0000 (21:20 +0000)
commit38d953b2ffd4e0cee9e77f97988e44be105023c6
treeedf0df8f8fe4a6b07a82d53a9436bbecc8bfb1f2
parent160a088fbe19d0b3c65040b9bc04cc8bdd3d0d24
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>
meta/classes-recipe/cargo.bbclass