Revision: 22131
Author: [email protected]
Date: Tue Jul 1 15:22:22 2014 UTC
Log: updated instructions to include new svn revs and "make builddeps"
http://code.google.com/p/v8/source/detail?r=22131
Modified:
/wiki/BuildingWithGYP.wiki
=======================================
--- /wiki/BuildingWithGYP.wiki Tue Feb 18 08:22:20 2014 UTC
+++ /wiki/BuildingWithGYP.wiki Tue Jul 1 15:22:22 2014 UTC
@@ -5,18 +5,20 @@
=Building V8=
V8 is built with the help of [http://code.google.com/p/gyp/ 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 compiler you're using.
-The instructions below assume that you already have a [UsingGit checkout
of V8].
+The instructions below assume that you already have a [UsingGit checkout
of V8] but haven't yet installed the build dependencies.
+If you intend to develop on V8, i.e., send patches and work with
changelists, you will need to install the dependencies as described
[UsingGit here].
+
==Prerequisite: Installing GYP==
First, you need GYP itself. On systems that have {{{make}}} (Linux, Mac,
most other Unixes), this is as easy as:
{{{
-make dependencies
+make builddeps
}}}
Otherwise (e.g. on Windows), you need to get GYP manually. From the root
of your V8 checkout, run:
{{{
-svn co http://gyp.googlecode.com/svn/trunk build/gyp
+svn co http://gyp.googlecode.com/svn/trunk build/gyp --revision 1831
}}}
==Building==
@@ -28,7 +30,7 @@
====Build instructions====
-The top-level Makefile defines a number of targets for each target
architecture ({{{ia32}}}, {{{x64}}}, {{{arm}}}) and mode ({{{debug}}} or
{{{release}}}). So your basic command for building is:
+The top-level Makefile defines a number of targets for each target
architecture ({{{ia32}}}, {{{x64}}}, {{{arm}}}, {{{arm64}}}) and mode
({{{debug}}}, {{{optdebug}}}, or {{{release}}}). So your basic command for
building is:
{{{
make ia32.release
}}}
@@ -93,7 +95,13 @@
Building with clang works on both Mac and Linux. You can use the same
Makefile and instructions as when building with GCC, just a few extra steps
are required first:
{{{
export CXX=/path/to/clang++
+export CC=/path/tp/clang
+export CPP="/path/to/clang -E"
export LINK=/path/to/clang++
+export CXX_host=/path/to/clang++
+export CC_host=/path/tp/clang
+export CPP_host="/path/to/clang -E"
+export LINK_host=/path/to/clang++
export GYP_DEFINES="clang=1"
}}}
After that, you can simply call {{{make}}} with any target as discussed in
the [BuildingWithGYP#GCC_+_make GCC + make] section.
@@ -146,17 +154,17 @@
* Use the Windows installer from http://python.org/download
* Check out the version provided by Chromium:
{{{
-svn co http://src.chromium.org/svn/trunk/tools/third_party/python_26@89111
third_party/python_26
+svn co http://src.chromium.org/svn/trunk/tools/third_party/python_26
third_party/python_26 --revision 89111
}}}
* Use a cygwin shell instead of the normal Windows command prompt.
Either way, it is recommended to put python.exe into your PATH.
# The Chromium-provided cygwin installation. This is *absolutely
required*, your build will fail if you don't do this:
{{{
-svn co http://src.chromium.org/svn/trunk/deps/third_party/cygwin@231940
third_party/cygwin
+svn co http://src.chromium.org/svn/trunk/deps/third_party/cygwin
third_party/cygwin --revision 66844
}}}
# ICU.
{{{
-svn co https://src.chromium.org/chrome/trunk/deps/third_party/icu46
third_party/icu
+svn co https://src.chromium.org/chrome/trunk/deps/third_party/icu46
third_party/icu --revision 258359
}}}
====Building====
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
