On Mon, 11 Dec 2023 at 10:09, Alex Kiernan <alex.kier...@gmail.com> wrote:
> In a single project there are (potentially) multiple Cargo.toml, but
> just one Cargo.lock. If there's multiple Cargo.lock files in a repo,
> that implies multiple projects which I don't think we've any way of
> building from a single recipe.
I'm thinking of projects like librsvg, python3-bcrypt or
python3-cryptography where the build is orchestrated by meson,
autoconf or setuptools, and where we don't run cargo directly and
leave it to those tools. They may have single Cargo.lock now, but will
that hold? Also, that Cargo.lock is not necessarily in the root of
${S}, so you'd have to set the location manually, instead of not
having to worry about it. Is CARGO_LOCK_PATH or its parent variables
already set correctly for all of them? I see this is not done from
python3-cryptography; shouldn't the build error out, if
cargo_common_do_patch_paths requires the location? Something doesn't
compute fully here.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192150):
https://lists.openembedded.org/g/openembedded-core/message/192150
Mute This Topic: https://lists.openembedded.org/mt/103094777/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
