Skip to content

Commit

Permalink
chore(doc): [skip ci] updated SQLite3 and LevellDown native lib compile
Browse files Browse the repository at this point in the history
instructions / troubleshooting for Windows Visual Studio / MSBUILD 2017
vs. 2019
  • Loading branch information
danielweck committed Dec 8, 2021
1 parent ee0ad37 commit 1ed9fa4
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ TravisCI, `develop` branch:

1) NodeJS 14 (check with `node --version`)
2) NPM 6 (check with `npm --version`)
3) C++ compiler for native NodeJS modules (SQLite3 and LevelDown database backends), should work out of the box in Linux and MacOS. On Windows Visual Studio can be installed or simply call `npm install -g windows-build-tools`.
3) C++ compiler for native NodeJS modules (SQLite3 and LevelDown database backends), should work out of the box in Linux and MacOS. On Windows, Visual Studio can be installed, or simply call `npm install -g windows-build-tools`.

## Technologies

Expand All @@ -56,6 +56,8 @@ TravisCI, `develop` branch:
### Install dependencies

* `npm install` (or `npm ci`): initialize local `node_modules` packages from dependencies declared in `package.json` (this will also automatically call a long-running compilation stage in `npm run postinstall`)
* in case of failure to NPM "install" because of "Divina player" SHA integrity mismatch, please try running the following command in your shell: `node scripts/package-lock-patch.js && cat package-lock.json | grep -i divina-player-js` (this converts SSH GitHub references to HTTPS ones)
* in case of NPM / Node GYP failing to compile SQLite3 or LevelDown native libs in Windows under Visual Studio 2019's command line tools: `npm config set msvs_version 2019 --global` and `npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe"` (adjust with your own path, for example `Enterprise` or `Professional` instead of `Community`)

### Start application in development environment

Expand Down

0 comments on commit 1ed9fa4

Please sign in to comment.