17c1cf2865
crrev.com/1177163002 should have fixed the issues that broke this last time. Notes: - The current functionality is meant to stay. If you prefer the old way, just set v8_use_external_startup_data=0. - You might notice this if you call d8 via PATH. Either explicitly tell d8 where your external snapshot/built-ins are, or change the build options as above. - This follows Chromium practice, that mostly uses this feature these days. - Other platforms to follow later. BUG= Review URL: https://codereview.chromium.org/1189563004 Cr-Commit-Position: refs/heads/master@{#29050} |
||
---|---|---|
.. | ||
mac | ||
all.gyp | ||
android.gypi | ||
detect_v8_host_arch.py | ||
features.gypi | ||
get_landmines.py | ||
gyp_environment.py | ||
gyp_v8 | ||
gyp_v8.py | ||
landmine_utils.py | ||
landmines.py | ||
OWNERS | ||
README.txt | ||
shim_headers.gypi | ||
standalone.gypi | ||
toolchain.gypi |
For build instructions, please refer to: https://code.google.com/p/v8/wiki/BuildingWithGYP TL;DR version on *nix: $ make dependencies # Only needed once. $ make ia32.release -j8 $ make ia32.release.check # Optionally: run tests.