Windows-build-tools Download

[Geneva Andreotti]

Thereare built-in Node.js build tools, so it is recommended to use this. In fact, if you go on the npm or GitHub page of the windows-build-tools package, it will say that you should use the Node.js build tools.

To do this, go to the official Node.js download website, and download the LTS version. Then, run the installer. At a point in the installation, it will have a checkbox that says Automatically install the recommended tools. Make sure to check that!

Due to the Python error, as a result of my research on the internet, I learned that installing npm install --global windows-build-tools would solve my problem. However, when I was installing the package, I was using version 16 of NodeJS and I kept getting errors or it was interrupted.

I tried to install the Microsoft Visual C++ Build tools. The installer(filename is visualcppbuildtools_full.exe) stops right after the startof the installation it says a setup package is missing or damaged("EinSetuppaket fehlt oder ist beschdigt"). The option to download itagain doesnt work. Downloading the installer again doesnt help. Tryingto do an offline installation doesnt work either and I get the sameerror. How can I find out what exactly the problem is and how can Isolve it?

After installation, npm will automatically execute this module, which downloads and installs VisualC++ Build Tools, provided free of charge for most users by Microsoft (as part of Visual Studio Community, please consult the license to determine whether or not you're eligible). These tools are required to compile popular native modules.If not already installed, it will also install Python 2.7, configuring your machine and npm appropriately.

Both installations are conflict-free, meaning that they do not mess with existing installations ofVisual Studio, C++ Build Tools, or Python. If you see anything that indicates otherwise, pleasefile a bug.

By default, windows-build-tools will download the latest installers from Microsoft each timeit's installed. Alternatively, you can prepare a folder that contains installers. They need tohave their original names:

This package currently only handles the most common use case, none of the edge cases. If you encounter errors, we'd greatly appreciate error reports (and even pull requests). This is currently tested on Windows 10.

Ensure that the variables passed match your location of npm's roaming data and the locationof user profiles on your machine. For , substitute the name of the account you want toinstall windows-build-tools for. For more information, see the npm config set prefixdescription here.

The Python installation was made possible by Ali Hajimirza, who kindly wrestled with Python's MSIs until they surrendered. For details regarding the license agreements applicable to Python, see History and License 2.x and 3.x.

Use of Microsoft software is subject to the terms of the corresponding license agreements. For details regarding the license agreements applicable to Visual Studio products, refer to their License Directory page. (See also this discussion for the gist of it.)

The xPack Windows Build Tools is a Windows specific package,customised for the requirements of the Eclipse CDT managed buildprojects. It includes a recent version of GNU make and a recentversion of BusyBox, which provides a convenient implementationfor sh/rm/echo.

For those interested in technical details, if make does not find a shin the path, it falls back to using the Microsoft cmd.exe when launchingsub-processes. As with other Windows implementations, compared to Unixshells, cmd.exe is severely restricted, also impacting the make correctbehaviour.

Eclipse is a more or POSIX compliant environment, which favours the use ofstandard forward slashed for path separators, and all automaticallygenerated make files use this convention. The version of the make andsh commands packed by xPack Windows Build Tools also favourPOSIX standard forward slashes.

For those interested in building the binaries, please read theREADME-MAINTAINERpage.However, the ultimate source for details are the build scripts themselves,all available from the windows-build-tools-xpack.git/scriptsfolder.

How this should be done, however, is another problem. The simplest approach would be similar to windows-build-tools, i.e. publishing a dummy package to PyPI, and perform whatever tasks required in a custom setup.py. I am not very fond of this idea, however, since IMO it is a very bad idea to download and run arbitrary code, in general. Some other ideas from the top of my head:

Future pip integration is also something that we could discuss once we have it working. (I, personally, would really like to make pip a more complete tool with publishing, building and installing capabilities)

On macOS I can xcode-select --install; on Ubuntu python-dev provides everything I need. For Windows, however, I need to open the browser, search for VS2017 Build Tools, download, run it, and decide what components I want. It would be immensely helpful if there is a more streamlined path to do this.

3a8082e126