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

Add MS build tools #16

Open
eljefedelrodeodeljefe opened this issue Apr 10, 2017 · 9 comments
Open

Add MS build tools #16

eljefedelrodeodeljefe opened this issue Apr 10, 2017 · 9 comments
Assignees

Comments

@eljefedelrodeodeljefe
Copy link
Owner

Afaik, node-gyp now integrates MS build as binary, so users wouldn't depend on installed software. Getting and integrating this binary should be goal for this project.

@refack
Copy link

refack commented Apr 10, 2017

I don't like npm packages installing global stuff. Especialy MSVS (even the build tools) which is a cancer that changes so much things on your system.

What should be done, that node-gyp doesn't do, is fail early with an informative error that explains how to install. Maybe install only on user approval.

@eljefedelrodeodeljefe
Copy link
Owner Author

eljefedelrodeodeljefe commented Apr 10, 2017

I am pretty sure you can have the stuff locally. I'll look into it.

@refack
Copy link

refack commented Apr 10, 2017

I think the recommended solution by node-gyp is to install https://github.com/felixrieseberg/windows-build-tools with installs MSVS Buildtools. But I really dislike this.

@refack
Copy link

refack commented Apr 10, 2017

I am pretty sure you can have the stuff locally. I look into it.

I've looked into it, you can install the compiler, but not the SDK which is critical (has all the .h files). And windows-build-tools does a horrible job at that.

@refack
Copy link

refack commented Apr 10, 2017

@refack
Copy link

refack commented Apr 10, 2017

I just got a official answer from MS. The build tools are officially "xcopyable", the SDK isn't (officially). But it could be done, just need to either set some ENV vars or a few registry keys, for the two to find each other.
But it's huge (~3GB). I'll do a few compilations with an IO tracer to see which files are actually used.

@eljefedelrodeodeljefe
Copy link
Owner Author

After looking at it and your pointers above I am also doubtful that it should be integrated here. It's quite convoluted. I may only take the compiler an figure out a decent way to get the SDK or at least good install docs.

@refack
Copy link

refack commented Apr 16, 2017

It's been a long standing (5 years or more) dream of mine to get an xcopyable windows dev environment, or at least a simple recipe, since I have an aversion to Installers.
It's definatly getting closer.

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