Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Fix the package scripts #373

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.

Sign up for GitHub

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

Merged
maxkorp merged 1 commit into from
Jan 30, 2015
Merged

Fix the package scripts #373

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 3 additions & 10 deletions 13 README.md
View file
Open in desktop
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 15 package.json
View file
Open in desktop
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"
}
}
Morty Proxy This is a proxified and sanitized view of the page, visit original site.