a37040b275
We recently had some XP issues on chromium.win after https://codereview.chromium.org/19384011/. This might fix it - quote: "The most likely cause of the problem is a gyp (or similar) change that resulted in v8.dll linking against the release version of the crt (for a debug build). There are two MS VC related files: the crt and the c++ std lib (MSVCR100.DLL and MSVCP100D.DLL). The former is set to release, the latter to debug." I am not entirely sure if this change fits to the linker options for debug level 2. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/21776002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16026 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 |
||
---|---|---|
.. | ||
all.gyp | ||
android.gypi | ||
features.gypi | ||
gyp_v8 | ||
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.