max-mapper / max-mapper/screencat
Cannot build on Windows 7 64-bit
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3k
- Forks
- 354
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
It returns the following error when executing npm install after cloning the project or running npm install inside another project which has robotjs as a dependency.
npm install
> robotjs@0.4.5 install E:\robotjs
> prebuild --install
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.targets(44,5): error MSB8020: The builds tools for v140 (Platform Toolset = 'v140' ) cannot be found. To build using the v140 build tools, either click the Project menu or right-click the solution, and then select "Update VC++ Projects...". In stall v140 to build using the v140 build tools. [E:\robotjs\build\robotjs.vcxproj]
prebuild ERR! build error
prebuild ERR! stack Error: `msbuild` failed with exit code: 1
prebuild ERR! stack at ChildProcess.onExit (E:\robotjs\node_modules\node-gyp\lib\build.js:276:23)
prebuild ERR! stack at emitTwo (events.js:106:13)
prebuild ERR! stack at ChildProcess.emit (events.js:191:7)
prebuild ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
prebuild ERR! not ok
prebuild ERR! build Error: `msbuild` failed with exit code: 1
prebuild ERR! build at ChildProcess.onExit (E:\robotjs\node_modules\node-gyp\lib\build.js:276:23)
prebuild ERR! build at emitTwo (events.js:106:13)
prebuild ERR! build at ChildProcess.emit (events.js:191:7)
prebuild ERR! build at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\mattjs\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.9.2
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! robotjs@0.4.5 install: `prebuild --install`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the robotjs@0.4.5 install script 'prebuild --install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the robotjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! prebuild --install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs robotjs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls robotjs
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! E:\robotjs\npm-debug.log
Steps to Reproduce (for bugs)
- Clone this project
- cd to the location
- npm install
Context
I'm trying to build this from the source on a windows machine but can't get it to work either by installing via npm install or node-gyp rebuild --python "path-to-python" --msvs_version=2015
Your Environment
- Screencat version: 4.2.0
- RobotJS version: 0.4.5
- Node.js version: 6.9.2 32-bit
- npm version: 4.0.5
- node-gyp version: 3.4.0
- Python version: 2.7
- Visual Studio: 2015 Professional Update 3
- Operating System: Windows 7 SP1 64-bit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with npm install on the reported Windows 7, Node.js 6.9.2, and Visual Studio 2015 setup, then trace the prebuild --install and node-gyp MSBuild step shown in the log. Done means the project installs successfully without the v140 toolset error on the reported environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, nodejs
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100