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

Cannot determine MSVC on Windows ARM64 #15

Closed
Alovchin91 opened this issue Mar 13, 2021 · 4 comments
Closed

Cannot determine MSVC on Windows ARM64 #15

Alovchin91 opened this issue Mar 13, 2021 · 4 comments

Comments

@Alovchin91
Copy link

Hi,

The SetupConfiguration COM component currently cannot be used to determine MSVC installation on Windows ARM64.

This prevents tools like rustc from finding link.exe and C++ stdlib: rust-lang/rust#83043

The issue has been reported on Developer Community twice but both cases are as of now ignored:

https://developercommunity.visualstudio.com/t/setupconfiguration-doesnt-find-any-vs-installation/1232316
https://developercommunity.visualstudio.com/t/isetupconfiguration-is-not-registered-on-arm64/1236604

One of the easiest solutions would be to register an out-of-process DLL surrogate on ARM64: https://docs.microsoft.com/en-us/windows/win32/com/using-the-system-supplied-surrogate

This shouldn't be too hard to do so I hope somebody could do that in their Crafting days :)

Thanks!

@heaths
Copy link
Member

heaths commented Mar 15, 2021

The COM APIs and tools built on them like https://github.com/microsoft/vswhere are not designed nor contain enough information to find files within individual components. See the aforementioned link for samples, though, of how you can find various tools including a sample to find VC toolsets.

@heaths heaths closed this as completed Mar 15, 2021
@Alovchin91
Copy link
Author

@heaths Thank you for the response. This is not the exact issue; the same logic works perfectly in x86 and x64 processes. The issue is that the COM component cannot be accessed as-is from an arm64 process because it's supposed to run in-proc and it's only registered for x86 and x64.

I don't really know how to phrase the issue so that somebody at Microsoft finally gave it some proper attention 😞

@heaths
Copy link
Member

heaths commented Mar 15, 2021

I've forwarded on the request to the proper team.

@Alovchin91
Copy link
Author

Thanks!

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

No branches or pull requests

2 participants