Move Windows arm64 scripts from pytorch/builder

[iremyux]

This PR moves the Windows Arm64 scripts from the builder repository to the main repository. The corresponding PR to pytorch/builder that removes them is here : pytorch/builder#2058

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/144317

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 10da4d7 with merge base f52901a ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[seemethere]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[afrittoli]

@iremyux I'm trying to find out where bootstrap_libuv originates from - it looks like it was added in the PR, in commit "- openblas, libuv and tests update" as I don't think it ever existed in pytorch/build.

The reason I'm asking is that I'm working on the conda removal project, and libuv is one of the packages that is pulled from conda. We could use the bootstrap_libuv.bat script to build libuv for the supported architectures and store the resulting binaries in GitHub artifact or S3 for re-use. I don't see where bootstrap_libuv is invoked today, do you know how the script is used today?

[ozanMSFT]

Hey @afrittoli ; We've created bootstrap_libuv.bat to build libuv from source code for Windows ARM64.

This is necessary because conda does not support Windows ARM64. We compile the binary from the source code using MSVC and then copy the binaries to the target to enable the USE_DISTRIBUTED functionality for the PyTorch on Windows ARM64. This functionality was previously missing in the pytorch/builder project.

In theory, bootstrap_libuv.bat could also be used for other platforms, but we have not tested it on Windows x64 or other systems.

If possible, uploading it to an S3 Bucket or GitHub Artifact would be very helpful, allowing us to include it without rebuilding.

Regarding the usage:
Currently, we are updating and preparing Windows ARM64 workflows that will use these scripts. Once merged, these scripts will be used for the PyTorch Windows ARM64 distribution.

[afrittoli]

Hey @afrittoli ; We've created bootstrap_libuv.bat to build libuv from source code for Windows ARM64.

This is necessary because conda does not support Windows ARM64. We compile the binary from the source code using MSVC and then copy the binaries to the target to enable the USE_DISTRIBUTED functionality for the PyTorch on Windows ARM64. This functionality was previously missing in the pytorch/builder project.

In theory, bootstrap_libuv.bat could also be used for other platforms, but we have not tested it on Windows x64 or other systems.

If possible, uploading it to an S3 Bucket or GitHub Artifact would be very helpful, allowing us to include it without rebuilding.

Regarding the usage: Currently, we are updating and preparing Windows ARM64 workflows that will use these scripts. Once merged, these scripts will be used for the PyTorch Windows ARM64 distribution.

Cool, thanks.
I think it would make sense to streamline things and have both architectures use the same set of scripts, building from source and caching artefacts, rather than relying on coda for the amd64 case. @atalman WDYT?