[swift-build-dev] Using the update-checkout branch scheme facility

Tim Hawkins tim.thawkins at gmail.com
Thu Feb 2 17:50:00 CST 2017


Thanks Graydon, that's exactly what i was looking for.....


On Fri, Feb 3, 2017 at 2:14 AM Graydon Hoare <ghoare at apple.com> wrote:

> 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)
>
> Hth,
>
> -Graydon
>
> > On Feb 2, 2017, at 5:10 AM, Tim Hawkins via swift-build-dev <
> swift-build-dev at swift.org> 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
> > swift-build-dev at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-build-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20170202/faa6d2eb/attachment.html>


More information about the swift-build-dev mailing list