| OLD | NEW |
| 1 <font color='darkred'><b>Build issues? File a bug at code.google.com/p/v8/issues
or ask for help on v8-users@googlegroups.com.</b></font> | 1 **Build issues? File a bug at code.google.com/p/v8/issues or ask for help on v8-
users@googlegroups.com.** |
| 2 | 2 |
| 3 # Building V8 | 3 # Building V8 |
| 4 | 4 |
| 5 V8 is built with the help of [GYP](http://code.google.com/p/gyp/). GYP is a meta
build system of sorts, as it generates build files for a number of other build
systems. How you build therefore depends on what "back-end" build system and com
piler you're using. | 5 V8 is built with the help of [GYP](http://code.google.com/p/gyp/). GYP is a meta
build system of sorts, as it generates build files for a number of other build
systems. How you build therefore depends on what "back-end" build system and com
piler you're using. |
| 6 The instructions below assume that you already have a [checkout of V8](using_git
.md) but haven't yet installed the build dependencies. | 6 The instructions below assume that you already have a [checkout of V8](using_git
.md) but haven't yet installed the build dependencies. |
| 7 | 7 |
| 8 If you intend to develop on V8, i.e., send patches and work with changelists, yo
u will need to install the dependencies as described [here](using_git.md). | 8 If you intend to develop on V8, i.e., send patches and work with changelists, yo
u will need to install the dependencies as described [here](using_git.md). |
| 9 | 9 |
| 10 | 10 |
| 11 ## Prerequisite: Installing GYP | 11 ## Prerequisite: Installing GYP |
| (...skipping 192 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 204 ``` | 204 ``` |
| 205 > > > This will spit out a bunch of warnings about missing input files, but it s
eems to be OK to ignore them. (If you have time to figure this out, we'd happily
accept a patch that makes the warnings go away!) | 205 > > > This will spit out a bunch of warnings about missing input files, but it s
eems to be OK to ignore them. (If you have time to figure this out, we'd happily
accept a patch that makes the warnings go away!) |
| 206 1. Build: | 206 1. Build: |
| 207 ``` | 207 ``` |
| 208 /cygdrive/c/Program\ Files\ (x86)/Microsoft\ Visual\ Studio\ 9.0/Common7/IDE/dev
env.com /build Release build/all.sln | 208 /cygdrive/c/Program\ Files\ (x86)/Microsoft\ Visual\ Studio\ 9.0/Common7/IDE/dev
env.com /build Release build/all.sln |
| 209 ``` | 209 ``` |
| 210 | 210 |
| 211 | 211 |
| 212 #### Custom build settings | 212 #### Custom build settings |
| 213 | 213 |
| 214 See the "custom build settings" section for [Xcode](#Xcode.md) above. | 214 See the "custom build settings" section for [Xcode](#Xcode) above. |
| 215 | 215 |
| 216 | 216 |
| 217 #### Running tests | 217 #### Running tests |
| 218 | 218 |
| 219 You can abuse the test driver's --buildbot flag to make it find the executables
where MSVC puts them: | 219 You can abuse the test driver's --buildbot flag to make it find the executables
where MSVC puts them: |
| 220 ``` | 220 ``` |
| 221 python tools/run-tests.py --buildbot --outdir build --arch ia32 --mode Release | 221 python tools/run-tests.py --buildbot --outdir build --arch ia32 --mode Release |
| 222 ``` | 222 ``` |
| 223 | 223 |
| 224 | 224 |
| (...skipping 26 matching lines...) Expand all Loading... |
| 251 | 251 |
| 252 Building and testing: | 252 Building and testing: |
| 253 1. Open a MinGW shell | 253 1. Open a MinGW shell |
| 254 1. `tools/mingw-generate-makefiles.sh` _(re-run this any time a `*`.gyp`*` fil
e changed, such as after updating your checkout)_ | 254 1. `tools/mingw-generate-makefiles.sh` _(re-run this any time a `*`.gyp`*` fil
e changed, such as after updating your checkout)_ |
| 255 1. `make ia32.release` _(unfortunately -jX doesn't seem to work here)_ | 255 1. `make ia32.release` _(unfortunately -jX doesn't seem to work here)_ |
| 256 1. `make ia32.release.check -j8` | 256 1. `make ia32.release.check -j8` |
| 257 | 257 |
| 258 | 258 |
| 259 # Final Note | 259 # Final Note |
| 260 <font color='darkred'><b>If you have problems or questions, please file bugs at
code.google.com/p/v8/issues or send mail to v8-users@googlegroups.com. Comments
on this page are likely to go unnoticed and unanswered.</b></font> | 260 <font color='darkred'><b>If you have problems or questions, please file bugs at
code.google.com/p/v8/issues or send mail to v8-users@googlegroups.com. Comments
on this page are likely to go unnoticed and unanswered.</b></font> |
| OLD | NEW |