[please] about top-level makefiles build using GYP

56 views
Skip to first unread message

kishikun

unread,
Oct 30, 2012, 6:23:59 AM10/30/12
to v8-u...@googlegroups.com
is anyone can explain to me what is top-level makefiles build V8 using GYP in windows...i'm totally not understand it...sorry for my bad english

Jakob Kummerow

unread,
Oct 30, 2012, 6:47:29 AM10/30/12
to v8-u...@googlegroups.com
Read https://code.google.com/p/v8/wiki/BuildingWithGYP, in particular the "Visual Studio" section. The top-level Makefile is not used on Windows, because Windows doesn't have "make". Unless you use cygwin, which might work but is not officially supported.


On Tue, Oct 30, 2012 at 11:23 AM, kishikun <kishi...@gmail.com> wrote:
is anyone can explain to me what is top-level makefiles build V8 using GYP in windows...i'm totally not understand it...sorry for my bad english
Message has been deleted

kishikun

unread,
Oct 31, 2012, 3:18:39 AM10/31/12
to v8-u...@googlegroups.com
hi jacob, i've got this error when i tried to do make command, i thought that it must be executed on top-level makefile...could you explain to me how to build V8 on windows not using visual studio coz i'm prefer to use eclipse...sorry for my bad english :)

Jakob Kummerow

unread,
Oct 31, 2012, 3:31:30 AM10/31/12
to v8-u...@googlegroups.com
Seems to be a problem with your Cygwin installation (the file that generates the error is part of Cygwin, not part of V8). Sorry, but you're on your own on this, as building on Cygwin is not officially supported.

The officially supported compiler is Visual Studio. You don't need to use it for editing, as long as you have it installed so you can use its bundled compiler (which you can probably even configure to use from within Eclipse).

Sven Panne

unread,
Oct 31, 2012, 3:50:47 AM10/31/12
to v8-u...@googlegroups.com
To be correct, the problem is not in the Cygwin installation, the problem is in v8's #ifdef logic: WIN32 does not necessarily imply VisualStudio or MinGW. In the case at hand, we have a POSIX-compliant random(), but its signature doesn't match the POSIX one, which returns a long: http://www.unix.com/man-page/POSIX/3posix/random/.

Although Cygwin is not officially supported, we should nevertheless fix the signature and the #ifdef logic. For the latter, we should really, really move away from the totally broken and unmaintainable platform-centric #ifdefs towards feature-centric #ifdefs, a lesson the autotools community has learned 2-3 decades ago...

kishikun

unread,
Nov 1, 2012, 9:32:27 PM11/1/12
to v8-u...@googlegroups.com
oke jacob, i've got your point...thank for your answer :)
Reply all
Reply to author
Forward
Message has been deleted
0 new messages