I had to go spelunking in the build scripts to find this, so no idea if it is
the proper way, but it seems to work. In a fresh checkout of the swift repo:
./utils/update-checkout --clone --scheme swift-4.0-branch
This will clone all the needed repos and then check out the right branch.
-tim
> On Nov 16, 2017, at 6:30 AM, Geordie J via swift-dev <[email protected]>
> wrote:
>
> Hello,
>
> I recently asked about building a particular Swift release and couldn’t find
> the correct tag. It turns out there are two issues with this:
>
> 1. Somehow "git checkout swift-4.0.2-RELEASE” doesn’t work. In fact, the
> commit that tag references
> (https://github.com/apple/swift/commit/efb12f4d7a6aa7575333c13fbcdb7782426b130a
>
> <https://github.com/apple/swift/commit/efb12f4d7a6aa7575333c13fbcdb7782426b130a>)
> doesn’t seem to exist locally even after running “git fetch”, so I can’t
> even check out that commit’s parent and cherry-pick the release commit.
>
> This is spooky enough to make me think I’m doing something wrong: can someone
> confirm or deny that this release tag really exists outside of GitHub?
>
>
> 2. The “stable” branch of llvm (which is automatically referenced when I run
> utils/update-checkout) isn’t compatible with that tag (its parent commit at
> least). Frustratingly, checking out "swift-4.0-branch” in both apple/swift
> and apple/swift-llvm does not build on linux either. This appears to be due
> to a rename/move of Dwarf.h somewhere along the line.
>
> Any ideas?
>
>
> Thanks,
> Geordie
>
> _______________________________________________
> swift-dev mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-dev
_______________________________________________
swift-dev mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-dev
