The schemes are described in utils/update-checkout-config.json and are largely just named after the underlying branch names. Variation between scheme name and branch name seems to stem from variation in branch naming patterns in underlying repos (eg. stable vs. master) or variation in assembly of a combined scheme (eg. combining an upstream-with-swift branch in one repo with a master branch of another).
To build a swift-3.1-branch toolchain, I typically do the following:
$ utils/update-checkout --scheme swift-3.1-branch --clone --reset-to-remote
$ utils/build-script --release-debuginfo --llbuild --swiftpm
(Or other variants, depending on scenario)
On Feb 2, 2017, at 5:10 AM, Tim Hawkins via swift-build-dev <email@example.com> wrote:
I'm trying to work out how to use the --scheme BRANCH-SCHEME
command on update-checkout
In particular i'm trying to build swift-3.1-branch version of swift.
1) Does anybody have a sample of the syntax, --help is somewhat vauge
2) What are the repo/branch maps required for the 3.1 build?
swift-build-dev mailing list