Copying my response from another thread. The reason for this behavior is most likely caused by both Microsoft Visual Studio and MinGW being installed. The current SCons setup for V8 depends on the SCons autodetecting the toolchain, where MSVC is preferred over MinGW. You could try patching SConstruct and src/SConscript files adding tools = ['mingw'] to Environment() calls (Environment(tools = ['mingw'])). On a Windows installation with only MinGW installed V8 SCons build does not cause problems.
Regards, Søren On Wed, Apr 22, 2009 at 08:10, Qu0ll <[email protected]> wrote: > I really want to be able to use V8 in a MinGW project but I can't work out > how to build a compatible V8 library. Even when I run the command: > > *scons toolchain=gcc* > > to build V8 it tries to use the Microsoft cl command and fails miserably. > > *scons: Reading SConscript files ... > scons: done reading SConscript files. > scons: Building targets ... > cl /Foobj\release\dtoa-config.obj /c src\dtoa-config.c -Werror > -Wno-uninitialized -O3 -fomit-frame-p > ointer -fdata-sections -ffunction-sections -DWIN32 > /DENABLE_LOGGING_AND_PROFILING > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for > 80x86 > Copyright (C) Microsoft Corporation. All rights reserved.* > *cl : Command line error D8021 : invalid numeric argument '/Werror' > scons: *** [obj\release\dtoa-config.obj] Error 2 > scons: building terminated because of errors.* > > Has anyone managed to build V8 using gcc and/or MinGW? > > Thanks, > > -Qu0ll > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
