bpo-46744: Support "-Win32" and make platform flags case insensitive on Windows build scripts #31803
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
…in Windows build scripts.
|
Sorry, @conioh and @zooba, I could not cleanly backport this to |
|
GH-96282 is a backport of this pull request to the 3.11 branch. |
…in Windows build scripts. (pythonGH-31803) (cherry picked from commit 1288097) Co-authored-by: conioh <10606081+conioh@users.noreply.github.com>
…in Windows build scripts. (pythonGH-31803)
…in Windows build scripts. (GH-31803) Co-authored-by: conioh <10606081+conioh@users.noreply.github.com>
Minor issue I noticed during discussion in https://bugs.python.org/issue46744: The help string says to use "-ARM64" but the build script expects "-arm64".
This change makes the string compare case insensitive, makes the string compares for "-x86" and "-x64" case-insensitive too (just in case), and adds "-Win32" to the MSI build scripts to match the platform name passed to
PCBuild/build.bat.@zooba
https://bugs.python.org/issue46744