Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Just use env variables PROCESSOR_ARCHITEW6432/PROCESSOR_ARCHITECTURE on win32 #26

Open
CanadaHonk opened this issue Nov 22, 2023 · 0 comments · May be fixed by #27
Open

Just use env variables PROCESSOR_ARCHITEW6432/PROCESSOR_ARCHITECTURE on win32 #26

CanadaHonk opened this issue Nov 22, 2023 · 0 comments · May be fixed by #27

Comments

@CanadaHonk
Copy link

This seems a lot simpler and should work just as well?

CanadaHonk added a commit to CanadaHonk/arch that referenced this issue Nov 22, 2023
Just use environment variables `PROCESSOR_ARCHITEW6432`/`PROCESSOR_ARCHITECTURE` on win32 instead of checking paths. Closes feross#26.
@CanadaHonk CanadaHonk linked a pull request Nov 22, 2023 that will close this issue
CanadaHonk added a commit to CanadaHonk/arch that referenced this issue Feb 13, 2024
Just use environment variables `PROCESSOR_ARCHITEW6432`/`PROCESSOR_ARCHITECTURE` on win32 instead of checking paths. Closes feross#26.
CanadaHonk added a commit to CanadaHonk/arch that referenced this issue Feb 13, 2024
Just use environment variables `PROCESSOR_ARCHITEW6432`/`PROCESSOR_ARCHITECTURE` on win32 instead of checking paths. Closes feross#26.
CanadaHonk added a commit to CanadaHonk/arch that referenced this issue Feb 13, 2024
Just use environment variables `PROCESSOR_ARCHITEW6432`/`PROCESSOR_ARCHITECTURE` on win32 instead of checking paths. Closes feross#26.
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 a pull request may close this issue.

1 participant