8a43a3d761
Pick up the latest branch head for V8 4.7:
be169f8df0
Full change history for the 4.7 branch:
https://chromium.googlesource.com/v8/v8.git/+log/branch-heads/4.7
V8 blog post about what is new on V8 4.7:
http://v8project.blogspot.de/2015/10/v8-release-47.html
PR-URL: https://github.com/nodejs/node/pull/4106
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: rvagg - Rod Vagg <rod@vagg.org>
1.2 KiB
ECMAScript 402
V8 optionally implements the ECMAScript 402 API. The API is enabled by default, but can be turned off at compile time.
Prerequisites
The i18n implementation adds a dependency on ICU. If you run
make dependencies
a suitable version of ICU is checked out into third_party/icu.
Alternative ICU checkout
You can check out the ICU sources at a different location and define the gyp variable icu_gyp_path to point at the icu.gyp file.
System ICU
Last but not least, you can compile V8 against a version of ICU installed in your system. To do so, specify the gyp variable use_system_icu=1. If you also have want_separate_host_toolset enabled, the bundled ICU will still be compiled to generate the V8 snapshot. The system ICU will only be used for the target architecture.
Embedding V8
If you embed V8 in your application, but your application itself doesn't use ICU, you will need to initialize ICU before calling into V8 by executing:
v8::V8::InitializeICU();
It is safe to invoke this method if ICU was not compiled in, then it does nothing.
Compiling without i18n support
To build V8 without i18n support use
make i18nsupport=off native