On Thu, Nov 3, 2011 at 19:36, Stephan Beal <[email protected]> wrote:
> A note to the other gyp-uninitiated: be sure to tell it which platform you
> want to build for or it (apparently) tries to build several. e.g. it fails
> on my netbook if i just do 'make debug' because it tries to build the
> x86/64 build after the ia32 build is finished. i.e. use 'make ia32.debug'
> or 'make x64.debug', or similar.
>
Correct. This is a conscious choice for V8, because normally when you
change the source, you'll want to make sure that it still compiles/works on
all architectures (i.e. {ia32, x64, arm}×{release, debug}). If you only
want to build the release mode of what your local machine needs, there's
the "make native" target.
> PS: how do i set my install prefix using gyp? i always prefer
> --prefix=$HOME.
>
I don't believe gyp supports creating "install" targets at all.
Compile output (both object files and final binaries/libraries) goes to
./out/<arch>.<mode>/ by default, the "out/" part of that path can be
overridden with the OUTDIR= parameter to the top-level Makefile. Again,
this is documented at http://code.google.com/p/v8/wiki/BuildingWithGYP.
If you want to install the binaries to your file system, you'll need to add
support for that yourself. As always, patches are welcome (just make sure
they don't break integration with Chromium).
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
