Stream: t-compiler/help

Topic: build *only* a cross-compiler


Jake Goulding (Jul 04 2020 at 20:51, on Zulip):

When I set host, it says it will build a compiler in addition:

# In addition to the build triple, other triples to produce full compiler
# toolchains for. Each of these triples will be bootstrapped from the build
# triple and then will continue to bootstrap themselves. This platform must
# currently be able to run all of the triples provided here.
#
# Defaults to just the build triple
host = ["aarch64-apple-darwin"]

Is there a way to only build the cross-compiler?

/cc @simulacrum

Josh Triplett (Jul 04 2020 at 21:24, on Zulip):

@Jake Goulding That would imply building those cross-compilers with the stage0 compiler, rather than the stage1, right?

Jake Goulding (Jul 04 2020 at 21:27, on Zulip):

@Josh Triplett yes, which is what I’m doing now, AFAICT. I’m only building stage 1.

simulacrum (Jul 04 2020 at 21:56, on Zulip):

@Jake Goulding I don't think you can do it "automatically" but x.py build --target <whatever> --stage 2 src/tools/rustdoc might get you pretty much what you want

Jake Goulding (Jul 04 2020 at 21:57, on Zulip):
# In addition to all host triples, other triples to produce the standard library
# for. Each host triple will be used to produce a copy of the standard library
# for each target triple.
Jake Goulding (Jul 04 2020 at 21:58, on Zulip):

or do the --target (and maybe --host) command line options replace the array, instead of extending it?

simulacrum (Jul 05 2020 at 11:38, on Zulip):

Replace, I think, but not sure.

Last update: Sep 28 2020 at 16:15UTC