7f156ffefa
Currently, some builders are in a clobber-landmine loop. Clobber deletes the .landmines tracker (sigh). Difficult to know if we are right after a clobber or if it is first-time landmines deployment. Also, a landmine-triggered clobber right after a clobber is not possible. Different clobber methods for msvs, xcode and make all have different blacklists of files that are not deleted. After the branch point, all v8 branch builders have to be manually clobbered, because the appearance of the landmines.py script and the first landmine request are in the same branch CL. TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/457063002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23012 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 |
||
|---|---|---|
| .. | ||
| all.gyp | ||
| android.gypi | ||
| detect_v8_host_arch.py | ||
| features.gypi | ||
| get_landmines.py | ||
| gyp_v8 | ||
| gyp_v8.py | ||
| landmine_utils.py | ||
| landmines.py | ||
| 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.