I'm going to respond to various bits, if I miss something, please point it out, I probably just missed answering it.
I would love to get help here. I would like to improve the documentation on GitHub to make this more useful so people can get started more easily. What it amounts to roughly is downloading a few zip files, extracting them, and running with a set of flags. This is a regression as the MSI builds broke and Ive not gotten around to fixing them. That is still on my list, but of course help is welcome!
Something along the lines of:
python -m pip install --user azure-devops tabulate python swift-build.py --build-id VS2019 --latest-artifacts --filter windows-x64 --download
should download the latest zip files for you.
swift-build.py is in the
utilities directory in swift-build. Extract the contents to
C:\. You will need to add the following flags when invoking
-resource-dir C:/Library/Developer/Platforms/Windows.platform/Developer/SDKs/Windows.sdk/usr/lib/swift. You must invoke this in the
x64 Native Developer Command Prompt (or run
VsDevCmd -arch=amd64 -host_arch=amd64 prior to using Swift).
Yes, the docker work is something that I've been looking at to ease the introduction to Swift for new comers.
You could try, I've not tried that. Note that they are not sufficient for building for Windows currently (beyond a few missing files that I need to add), they need the user to provide the Windows SDK as I cannot redistribute that. You can find that as part of the VS Build Tools installer on Windows. That is, you need to run the docker container on Windows or somehow provide the necessary content.
Sadly, I've not made as much progress as I would have liked to. The CI work ended up taking a turn for the worse and required a lot more effort to get to a state where it could be useful and understandable. Im hoping that will wrap up soon and I can return to working on more interesting things. I have a back log of patches that is sufficient to get tools-support-core building and almost working enough to get swift-package-manager building and running on Windows. I haven't fully gotten it to bootstrap yet though. There are issues with paths, and some more issues regarding paths in Foundation that need to be addressed.
Correct, that is exactly what I have done for porting the packages that I have added CMake builds for. They were largely just enumerating the targets and sources.
They are just daily updates, I do not really have much in the way of testing. If you have the time or inclination to setup testing, Id be happy to see that work get merged.
It is for now. If I manage to get some time, Id like to setup 5.2 builds. For now, its just tracking master.
Id like to delete the development snapshots at some point since they seem pretty big and it seems silly to just grow the collection unbounded. But, Id probably retain stable snapshots of major releases for how ever long they let you keep the images.