Virtual manifests are not handled

[Phidelux]

I have a simple project consisting of a core library, the main package and a helper script:

project
|- Cargo.toml
|- lib
   |- Cargo.toml
|- pkg1
   |- Cargo.toml
|- pkg2
   |- Cargo.toml

The root Cargo.toml is virtual, meaning it only defines the workspace members:

[workspace]
members = ["lib", "pkg1", "pkg2"]

I would expect cargo-bitbake to generate a bitbake recipe including the dependencies for all three packages.

Thanks.

[dantliff-sqc]

This is still not handled in 0.3.16. I'm not sure what is required to make this work.

If it did work, I would expect it to follow the -p/--package selection mechanism of cargo, so something like:

$ cargo bitbake -p pkg1

This is because a recipe may only be needed for a specific package in the workspace, rather than for all packages.

bitbake -c update_crates also doesn't seem to like virtual manifests (workspaces) either, which is why I'm back looking at cargo-bitbake in 2025...

EDIT: If you have separate recipes for each crate in your workspace, then you've probably set something like S = "${WORKDIR}/workspace/bin/my-crate" to ensure that cargo build runs from the target crate's directory. In this case, bitbake -c update_crates works if you set CARGO_LOCK_SRC_DIR in your bitbake recipe to point to the workspace root (the directory where the workspace's Cargo.toml resides), rather than the default (your crate's Cargo.toml location).

S = "${WORKDIR}/workspace/bin/my-crate"
CARGO_LOCK_SRC_DIR := "${WORKDIR}/workspace"   # workspace's Cargo.toml is in here

However, if you have one recipe for your entire workspace, with S = ${WORKDIR}/workspace, then it will probably just work anyway.

Apologies for posting this on the cargo-bitbake repository, but maybe this helps someone, someday.