[build2] Rust

[Boris Kolpackov]

Matthew Krupcale <mkrupcale at matthewkrupcale.com> writes:

> On Thu, Jan 23, 2020 at 6:02 AM Boris Kolpackov <boris at codesynthesis.com> wrote:
> 
> > What I am thinking about is the ability to specify (say, in the
> > manifest) that libfoo comes from a "foreign" package manager/repository
> > and have bpkg automatically call that manager to build it.
> 
> I see. To clarify, you're talking about a level above the build
> system, so the foreign package manager might itself use some
> alternative build system (in the case of non-binary, source packages),
> right?

Yes, that's correct. In case of Cargo the package manager and the
build system are basically fused so there is no any other way (except
perhaps that build plan idea).



> That is, this is separate from bpkg invoking other build systems
> directly?

Yes. If we want to go this route, then it probably makes more sense
to make build2 (the build system) invoke other build systems. In
fact, there were ideas of re-packaging vcpkg libraries as bpkg
packages and then writing a build system module that would invoke
CMake to build them and then present the result in a build2-native
form.