I've only ever built the 32-bit version with VS2008, and haven't had problems with either release or debug. I haven't had any experience building the x64 version.
matt On Sat, Jul 10, 2010 at 10:09 PM, Ashley <[email protected]> wrote: > Thanks Matt. I can get scons to build OK (which also compiles in my > other project) with: > scons mode=release library=static arch=x64 > But when I switch it to debug: > scons mode=debug library=static arch=x64 > I get a warning in spaces.cc which triggers an error due to /WX: > > cl /Foobj\debug\spaces.obj /c src\spaces.cc /nologo /W3 /WX /wd4355 / > wd4800 /MTd /Od /Gm /GR- /Gy /nologo /W3 /WX /wd435 > 5 /wd4800 /MTd /Od /Gm /DWIN32 /DV8_TARGET_ARCH_X64 /D_DEBUG / > DENABLE_DISASSEMBLER /DDEBUG /DENABLE_VMSTATE_TRACKING /DE > NABLE_LOGGING_AND_PROFILING /DV8_ENABLE_CHECKS / > DENABLE_DEBUGGER_SUPPORT /Isrc /Zi > spaces.cc > d:\v8\src\spaces.cc(1461) : error C2220: warning treated as error - no > 'object' file generated > d:\v8\src\spaces.cc(1461) : warning C4789: destination of memory copy > is too small > scons: *** [obj\debug\spaces.obj] Error 2 > scons: building terminated because of errors. > > Any idea what's wrong here? Can I work around by disabling /WX via > scons? > > Thanks > > On Jul 11, 2:21 am, Matt Seegmiller <[email protected]> wrote: >> In my experience building v8 on windows, it's always worked fine >> building with scons once I've had it set up. I've never had much luck >> building it from visual studio, and just treated the included solution >> file as something useful to browse through the source, not something >> that was meant to build it with. >> >> matt >> >> On Sat, Jul 10, 2010 at 9:19 PM, Ashley <[email protected]> wrote: >> > Hi all, >> >> > I'm having a few problems building V8 under Windows with VS2010. I've >> > followed the steps on 'Building on Windows' from the Wiki, such as >> > setting up environment variables, installing Python and scons, etc. I >> > then opened v8_x64.sln from v8\tools\visual_studio and converted it in >> > VS2010. It builds, but emits warnings: >> >> > 1>------ Rebuild All started: Project: v8_base, Configuration: Release >> > x64 ------ >> > ... >> > 1>regexp-macro-assembler-irregexp.obj : warning LNK4221: This object >> > file does not define any previously undefined public symbols, so it >> > will not be used by any link operation that consumes this library >> > 1>property.obj : warning LNK4221: This object file does not define any >> > previously undefined public symbols, so it will not be used by any >> > link operation that consumes this library >> > ... >> > 2>------ Rebuild All started: Project: v8, Configuration: Release x64 >> > ------ >> > ... >> > 2>v8_base.lib(property.obj) : warning LNK4221: This object file does >> > not define any previously undefined public symbols, so it will not be >> > used by any link operation that consumes this library >> > 2>v8_base.lib(regexp-macro-assembler-irregexp.obj) : warning LNK4221: >> > This object file does not define any previously undefined public >> > symbols, so it will not be used by any link operation that consumes >> > this library >> > ... >> > ========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ========== >> >> > I'm suspicious of these warnings, because although I get the .lib >> > files built OK, when I try to compile a project including v8.h and the >> > libs, I get the error: >> >> >>v8_x64.lib(conversions.obj) : error LNK2001: unresolved external symbol >> >>"bool __cdecl v8::internal::DoubleToAscii(double,enum >> >>v8::internal::DtoaMode,int,class v8::internal::Vector<char>,int *,int >> >>*,int *)" >> >>(?doubletoas...@internal@v8@@ya_nnw4dtoam...@12@hv?$vec...@d@1...@peah22@Z) >> >> > Any ideas on what's wrong here? >> >> > Thanks for any help. >> >> > -- >> > v8-users mailing list >> > [email protected] >> >http://groups.google.com/group/v8-users > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
