1864624 - Permit extending gkrust build in mozilla-central derived projects

Status: RESOLVED FIXED

(Firefox Build System :: General, enhancement)

Description

[Ikey Doherty]

Following on from 1860246, it was requested that instead of trying to merge two RustLibrary invocations, we instead allow shifting the gkrust build into the derived project, i.e. within comm-central.

This would allow comm-central to have its own Rust workspace, and build the upstream gkrust-shared library in the same unified build.

Note, investigation shows that due to the way config/ and / are laid out, the toplevel dir takes responsibility for .cargo/config installation, thus making it configurable. This is is to support comm-central using its own vendor tree, due to having no way in cargo to recreate the state of crates.io at the time of mozilla-central cargo.lock creation.

Comment 1

[Ikey Doherty]

Attachment: Bug 1864624: Support building gkrust in mozilla-central derived projects. r=glandium

Allow overriding the .cargo/config.in source location to permit projects such
as comm-central to provide their own vendor configuration and tree, as well as
conditionally building gkrust.

It is expected in comm-central that we still export and provide a gkrust build
by including the existing /toolkit/library/rust/moz.build into our build system,
such that gtest linkage and mozilla-central expectations are correctly met.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/895aff394004
Support building gkrust in mozilla-central derived projects. r=glandium

Comment 3

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/895aff394004