Skip to content

Add Windows ARM64 and x86 platform support to install scripts#652

Open
AlexVTor wants to merge 4 commits intomasterfrom
users/alextorres/UpdateInstallScripts
Open

Add Windows ARM64 and x86 platform support to install scripts#652
AlexVTor wants to merge 4 commits intomasterfrom
users/alextorres/UpdateInstallScripts

Conversation

@AlexVTor
Copy link
Contributor

installcredprovider.ps1

  • Added x86 architecture mapping to the switch block in Get-RuntimeIdentifier
  • Removed the win-arm64 -> win-x64 remap that forced ARM64 Windows onto the x64 binary

installcredprovider.sh

  • Added i386 | i686 | x86 architecture case to set_runtime_identifier
  • Removed the win-arm64 -> win-x64 remap that previously forced ARM64 Windows onto the x64 binary

Notes

These script changes are a prerequisite for the upcoming release that will include win-arm64 and win-x86 build artifacts. The install scripts will work end-to-end once those assets are published.

$osArch = "-x86"
}
else {
return ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to write the warning here too ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO it isn't necessary in either, but i'll add it for parity.
If I was a linux x86 user and I saw a message about windows x86, I would think it's a bit odd to see messaging related to a separate platform and their supported infra.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would a continue be better than returning empty and that way the default warning is used instead

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here and in the sh file as well if theres an equivalent

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neither powershell nor bash have a clean way to enter the default case inside a switch statement. I think what we have in the PR is the cleanest way to get the behavior we want

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants