Is it possible to compile v8 with MinGW?

[slavik]

Every instruction which I found describe how to build v8 with MinGW using Scons. But Scons is now deprecated. Is there a way to use GYP with MinGW?

http://code.google.com/p/v8/issues/detail?id=64

[Jakob Kummerow]

Building on MinGW is not officially supported, but should either work as it is or can probably be made to work with little changes (don't know, never tried it myself). 

In case any adaptations are necessary, we'd be happy to accept contributions, both patches[*] to V8 itself and documentation to be added to our wiki.

The general idea is to use build/gyp_v8 to produce project files for your toolchain (I assume this is make+GCC on MinGW?), then compile those project files as you normally do with that toolchain. The top-level Makefile automates both steps for Unix-like host systems, so you can easily do "make ia32.release" and so on.

[*] Please see http://code.google.com/p/v8/wiki/Contributing

[Slavic V]

I tried "make ia32.release"

It gives me following
make[1]: Entering directory `/d/projects/libv81/vendor/v8/out'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/d/projects/libv81/vendor/v8/out'

But i didn't alter gyp or make files. Just change compiler an linker
through env variables. So I assume on windows it tries to generate
msvc project and nothing more.

2012/6/23 Jakob Kummerow <jkum...@chromium.org>:

> --
> v8-users mailing list
> v8-u...@googlegroups.com
> http://groups.google.com/group/v8-users

[slavik]

If anybody was interesting if it possible to build current v8 with MinGW on windows. Yes, use following command  scons os=win32 toolchain=gcc library=shared

[Jakob Kummerow]

On Thu, Jun 28, 2012 at 1:07 PM, slavik <slav...@gmail.com> wrote:

If anybody was interesting if it possible to build current v8 with MinGW on windows. Yes, use following command  scons os=win32 toolchain=gcc library=shared

That might work for now, but as it tells you in the output, building V8 with SCons is deprecated and will not work much longer. You should use GYP instead.

[Slavic V]

I would be happy to use GYP, but it doesn't support MinGW. And I have
no clue how to hack GYP to support MinGW (even where to start from). I
take a look code of the GYP. It is harcoded to use msvs on windows.

2012/6/28 Jakob Kummerow <jkum...@chromium.org>:

[Mat Sutcliffe]

Sorry to necro a year-old thread, but this seemed like the best way to announce that I've been able to build Node.js in MinGW+MSYS quite easily - the trick is to use an MSYS build of Python. Node of course includes a bundled copy of v8, so this suggests that it should also be possible to build a standalone v8 in MSYS. See this blog post for details:
http://opensourcepack.blogspot.co.uk/2013/06/nodejs-with-posix-path-support.html

[Jakob Kummerow]

See also https://code.google.com/p/v8/wiki/BuildingWithGYP#MinGW.

--

--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users

---
You received this message because you are subscribed to the Google Groups "v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[M Morrison]

Is there any tips or tutorials on installinstalling for 64bit minge?? Or even cross-compiling with linux?

(have been successful in compiling for linux, mac and mingw32 as well as with visual studio 32 and 64)