This repository has been archived by the owner on Sep 11, 2021. It is now read-only.
windows-build-tools not installing Windows SDK 8.1? #9
Comments
|
@chadly Thank you for reporting this error. Unfortunately, I'm unable to reproduce the problem. Having said that, I cannot get the project to build by running the following commands on a clean install of Windows 10 on a VM. npm install windows-build-tools -g
npm install aglioNor by fallowing the instructions on Windows installation for node-gyp Both those methods result in different build errors. Are you able to install |
|
@chadly did you figure out a work around? I'm having the same problem |
|
@kneumei @chadly are you guys able to install any of these packages? |
|
I did not try any of those, but I did try I switched to using the "normal" instructions for building with node-gyp instead of using I'm not sure if this makes a difference or not, but I had installed vs 2015 + cpp tools already on my machine before installing |
|
having similar problem with npm install oracledb. it complains with: |
|
I think the important command is: |
|
Got the same error re no Windows 8.1 SDK. Does it depend on C++ being installed with VS 2015 to get the Windows SDK? Or maybe we should simply install the Windows 8.1 SDK? |
|
I'm getting the same error whilst trying to install the I'm using Windows 10 Enterprise latest and Visual Studio 2015. |
|
I believe I have found the cause of the problem:
It seems likely that this package does not check that the installers exited cleanly, or rather, did not verify the installation was successful. |
|
@replete windows-build-tools/ps1/launch-installer.ps1 Lines 26 to 28 in 042c134 |
|
By coincidence, I had just done this. The log file appear to confirm the issue: Full log file: |
|
I am going to run the Visual Studio setup, in hopes that I can add the 'Visual C++ Build Tools' - EDIT: The only related options in the 'Modify' workflow of the 'Visual Studio Installer' is to either install the 3GB Windows 10/8.1 SDK or install full support for 'Visual C++ projects', which is also 3GB. |
|
My problems disappeared after installing 'Visual C++' support in Visual Studio 2015 by re-running the installer. To summarize:
This workaround is not a satisfactory long-term solution because it demands 3GB of space to be consumed with unutilized resources. |
|
following up on @replete's tip (which worked for me - thanks!): on a fresh install of VS 2015, the application will prompt you to install the visual c++ build tools (which includes the windows 8.1 sdk) when you click "create new c++ project" - i stumbled over this at first |
|
@felixrieseberg |
|
VC++ Build Tools 2015 will fail install if VS 2015 is installed. This is a design issue, but also a technical issue. I completely endorse #1056 because the 2017 VS installer is designed to let you just lay down the tools you need. You should be able to install the C++ workload in VS 2015 or install the Win 8.1 SDK directly but LMK if you are blocked. |
|
Just had this issue trying to build with I installed VS community today, so it should be the 2017 installer as you said and should not have had this issue. This happens both with and without |
|
@AndrewPardoe let me know if there are better standard parameters or different packages we should install - I'd personally love to make the 8.1 SDK available to people (because it still seems like the default for a few native Node modules out there). |
VS 2017 installer has Windows 8.1 SDK as an option in the "Desktop development with C++" workload. Are you installing from the command line or clicking through the UI? |
|
Through the UI.
…On Jan 20, 2017 15:23, "Andrew Pardoe" ***@***.***> wrote:
I installed VS community today, so it should be the 2017 installer as you
said and should not have had this issue.
VS 2017 installer has Windows 8.1 SDK as an option in
the "Desktop development with C++" workload. Are you installing from the
command line or clicking through the UI?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWOLoamQPU4_a0X7ORUoE2nGQhdVDKCvks5rUQmmgaJpZM4JDMNS>
.
|
|
So then I'm confused about the issue. 8.1 is an option in the UI. Does just selecting it in the UI not work for you? |
|
Lol I installed only once. It took 3 days to download and install so I'm a
bit reluctant to uninstalling it, but if it's necessary I will. I did not
know that the recommended option did not include that.
…On Jan 20, 2017 18:38, "Andrew Pardoe" ***@***.***> wrote:
So then I'm confused about the issue. 8.1 is an option in the UI. Does
just selecting it in the UI not work for you?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWOLocoHjh4gdV2nqmBolnwxDXemNxJ9ks5rUTdPgaJpZM4JDMNS>
.
|
|
If you rerun setup it should give you an option to modify the install. You can include the SDK at that point. It should be much faster to download just the setup + the SDK. 3 days is really long. Bad internet where you live? You might consider using an ISO. |
|
Yes, Venezuela. Also I had to reset the set up various times because it got
interrupted or stuck due to irregular connection. And I will try that.
Thanks for the advice.
…On Jan 20, 2017 19:59, "Andrew Pardoe" ***@***.***> wrote:
If you rerun setup it should give you an option to modify the install. You
can include the SDK at that point. It should be much faster to download
just the setup + the SDK.
3 days is really long. Bad internet where you live? You might consider
using an ISO.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWOLoTHsYI_FJVFkPpweDPD2-4VLWvbRks5rUUpIgaJpZM4JDMNS>
.
|
|
For reference, the VS 2017 installer has two major changes that impact this scenario:
More about the VS 2017 installer can be found on the Visual Studio blog, e.g., https://blogs.msdn.microsoft.com/visualstudio/2016/06/17/redesigning-visual-studio-installation/ Also, if you're in a situation where you can download everything to create an offline install, you can do that with VS 2017: https://docs.microsoft.com/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio |
|
I really think some windows updates break it. I was able to compile native modules like a week ago, but now it tells me it cannot find Windows SDK 8.1. There is a really high chance it is actually caused by windows' updates because since windows 10, windows updates regularly breaks stuff (network, font render, etc...). Surely Microsoft developers did not even lint nor try their code before uploading to windows update server. Again, I am sure, the compile thing was working a week ago but now it is not. The only thing I can think of that changed my computer is windows update. UPDATE: After reinstalling the windows, everything seems working again... That will be your last choice to solve this problem if others' did not work. |
|
I installed the Visual C++ tools and 8.1 SDK from within Visual Studio when trying to create a new C++ project. After that it worked. This didn't need to uninstall Visual Studio first. |
|
My solution
|
|
@vmatt it's more easier to click on New Project and select c++ one. It will display the download option too. |
|
Thank you for all of you. I solved my problem through modified visual studio 2015 installation. |
|
i m getting error like this while installing loopback-cli C:\Users\Rajendra\AppData\Roaming\npm\node_modules\loopback-cli\node_modules\ursa>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) |
|
some one plz help out this |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From the comment here, it seems like installing
windows-build-toolsshould also install the Windows SDK 8.1.From a win 10 machine, I ran (from administrator cmd prompt):
with this output:
Relevant line being
MSB8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK...Is this something
windows-build-toolsshould have installed and made available?The text was updated successfully, but these errors were encountered: