Simple Mac OS compile Node-webkit tutorial

1 download depot_tools,zip download, direct git under clone
2) Depot_tools environment variable
3) gclient Sync
A) Python downloads can not be installed, you may manually install python2.7.6, copy Python.exe to Depot_tools
b) git download not installed, you can manually install GIT, set environment variables to the bin path
c) sync will first download chromium.src, 1.5G, if you use Gclient Sync will always make mistakes, because too big, the domestic environment we all understand. Therefore, it is recommended to use the GitHub client to clone,clone down and rename to Node-webkit/src
D later will clone88 a project, the process is very annoyed, the session for a long time, googlesource.com network is not very stable, so the first to add a domain name resolution, will be faster, if it is GitHub project, the proposal with C), with the client download after the directory. The clones here are the configuration items in the Deps.git file under CHROMIUM.SRC.

e) After all 88 items have been clone completed, Gclient will install Llvm/clang and compile. I am using OS X 11, which always prompts Clang:error:invalid deployment target for-stdlib=libc++ (requires OS X 10.7 or later).

Solution for modifying

node_webkit/src/tools/clang/scripts/update.sh macosx_deployment_target=10.5 ==> MACOSX_DEPLOYMENT_TARGET=10.7

f) on OS X you'll be the error messages reporting cycle in. gyp file dependency graph detected. It can be ignored because Gclient wants to run Gyp_chromium without a switch we need. The "on" to "Build" section
Error:command/usr/bin/python Src/build/gyp_chromium returned Non-zero exit status 1 in/users/gexin/documents/nw_ Workspace/node_webkit
Hook '/usr/bin/python src/build/gyp_chromium ' took 42.73 secs

g) CD NODE-WEBKIT/SRC
Export gyp_generators= ' Ninja '
./build/gyp_chromium Content/content.gyp
Ninja-c Out/release Nw-j4