-
Notifications
You must be signed in to change notification settings - Fork 752
Find msbuild.exe location from registry #13
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
Comments
I can take a look at that |
hmmm, turns out this is a bit more tricky. The RGiesecke.DllExport tool depends on being able to find lib.exe, and as far as I can tell that's not included in the Windows SDK, only in Visual Studio. Is it that much of a problem to have to have visual studio installed? I'd imagine most people building extensions would have it (or at least the express version). |
Certainly not an important point. I'm moving it to a backlog, if someone at some point wants to take a crack at this, great, otherwise we will just ignore. |
I implemented this in #18 now for two reasons: I'm trying out appveyor for a windows ci solution and it doesn't have vs installed, and a newer rgiesecke version might not require access to lib.exe, so we might be good on that one as well. |
Partially merge pythonnet/pull/13
Currently setup.py is using msvc9compiler.MSVCCompiler's find_exe method to find the location of msbuild.exe. That doesn't work unless VS is installed. We should probably be able to find the msbuild location by reading the official location from the registry, thus removing the dependency on VS.
The text was updated successfully, but these errors were encountered: