Skip to content

Comments

Handle known architectures with case statement#33

Open
theseion wants to merge 3 commits intopharo-project:masterfrom
theseion:32-AppVeyor-builds-for-Pharo-on-Windows-fail-because-theres-no-i686-architecture
Open

Handle known architectures with case statement#33
theseion wants to merge 3 commits intopharo-project:masterfrom
theseion:32-AppVeyor-builds-for-Pharo-on-Windows-fail-because-theres-no-i686-architecture

Conversation

@theseion
Copy link

Added a case statement that checks for known architecture variants. Will also assign UNKNOWN to the variable, similar to the OSNAME variable.

Fixes #32

@theseion
Copy link
Author

Since there are no more 32-bit VMs for Pharo 9+ there is no need to generate 32-bit architecture file names. However, the variable VM_ARCH is now handled the same way as OSNAME and will fallback to and UNKNOWN value for unknown architectures.

@theseion theseion changed the title Handle 32-bit architectures as well Handle known architectures with case statement May 26, 2021
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.

AppVeyor builds for Pharo on Windows fail because there's no i686 architecture

1 participant