FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Fix the package scripts by maxkorp · Pull Request #373 · nodegit/nodegit · GitHub

Repository navigation

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension .json  (1) .md  (1) All 2 file types selected
Only manifest files
Viewed files
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Unified
Split
Hide whitespace
Diff view
Unified
Split
Hide whitespace
13 changes: 3 additions & 10 deletions README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Original file line number Diff line number Diff line change
Expand Up @@ -74,18 +74,11 @@ In order to track down possible bugs, you will need a debug buid so you
can get a backtrace with [gdb](http://www.gnu.org/software/gdb/) or
[lldb](http://lldb.llvm.org/).

In order to do so, follow these steps:
If you're building for the first time, run `npm run installDebug` (or `BUILD_ONLY=true npm link`)

1. `BUILD_ONLY=true npm install` (or `BUILD_ONLY=true npm link`)
3. `node-gyp rebuild --debug` (the same as `node-gyp clean configure --debug build`)
Note that you should run `rm -rf build/Release` (or `rd /s /q build/Release` in Windows) to make sure a release build doesn't get loaded instead of the debug build.

If you're doing a subsequent rebuild of NodeGit in debug, the clean function will cause
a lot of extraneous recompilation of things you probably didn't change (like the vendor
dependencies).

1. `BUILD_ONLY=true npm install` (or `BUILD_ONLY=true npm link`)
2. `rm -rf build/Release` to make sure a release build doesnt get loaded instead of the debug build.
3. `node-gyp configure build --debug`
If you're doing a subsequent rebuild of NodeGit in debug, the clean function will cause a lot of extraneous recompilation of things you probably didn't change (like the vendor dependencies). If you need to regenerate the C++ files and recompile you can run `npm run rebuildDebug`, or `npm run recompileDebug` if you've manually updated the C++ files and don't want them to regenerate.

### Installing dependencies: ###

Expand Down
15 changes: 11 additions & 4 deletions package.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Original file line number Diff line number Diff line change
Expand Up @@ -85,15 +85,22 @@
"mocha": "mocha test/runner test/tests",
"mochaDebug": "mocha --debug-brk test/runner test/tests",
"test": "npm run lint && npm run cov",

"generateJson": "node generate/scripts/generateJson",
"generateNativeCode": "node generate/scripts/generateNativeCode",
"generateMissingTests": "node generate/scripts/generateMissingTests",


"prepublish": "node lifecycleScripts/prepareForBuild.js",
"publish": "node-pre-gyp package && node-pre-gyp publish",

"install": "node lifecycleScripts/install",
"installDebug": "BUILD_DEBUG=true npm install",
"postinstall": "node lifecycleScripts/clean",
"recompile": "BUILD_ONLY=true npm install",
"rebuild": "BUILD_ONLY=true node generate && node-gyp configure build",
"buildDebug": "node generate && BUILD_DEBUG=true npm install",
"prepublish": "node lifecycleScripts/prepareForBuild.js"

"recompile": "node-gyp configure build",
"rebuild": "node generate && node-gyp configure build",
"recompileDebug": "node-gyp configure --debug build",
"rebuildDebug": "node generate && node-gyp configure --debug build"
}
}

Back | FazBrowse Home | New Git URL