Doh, thanks, now I feel like an idiot.

What's the reason for having to use /MT instead of /MD? The rest of my
app uses /MD - isn't it dangerous to be mixing them?

garry


On Sep 26, 12:40 pm, "Søren Gjesse" <[EMAIL PROTECTED]> wrote:
> When compiling an application using v8.dll remember to
> define USING_V8_SHARED, see 
> <http://code.google.com/p/v8/wiki/BuildingOnWindows>http://code.google.com/p/v8/wiki/BuildingOnWindows
> <http://code.google.com/p/v8/wiki/BuildingOnWindows>section
> "Building the hello_world sample on Windows" where there is an example on
> linking with v8.dll.
> When building the v8.dll in release mode you should use /MT, as you should
> when compiling you application in release mode. Use /MTd for both in debug
> mode.
>
> Regards,
> Søren
>
> On Fri, Sep 26, 2008 at 12:47 PM, Garry <[EMAIL PROTECTED]> wrote:
>
> > I'm getting this liner error:
>
> > >> TestV8.obj : error LNK2001: unresolved external symbol "private: static
> > class v8::HandleScope::Data v8::HandleScope::current_"
> > ([EMAIL PROTECTED]@v8@@[EMAIL PROTECTED]@A)
>
> > Compiling v8 using this line:
>
> > >> scons mode=release snapshot=on library=shared
>
> > At first I thought it could have been because my target app uses /MD,
> > and the library uses /MT, so after fixing that:
>
> > >> d:\...\trunk\src\third_party/dtoa/dtoa.c(1528) : error C2220: warning
> > treated as error - no 'object' file generated
> > >> d:\...\googlev8\trunk\src\third_party/dtoa/dtoa.c(1528) : warning C4273:
> > 'gay_strtod' : inconsistent dll linkage
>
> > But after removing /WX (treat warning as error) I get the same result:
>
> > TestV8.obj : error LNK2001: unresolved external symbol "private:
> > static class v8::HandleScope::Data v8::HandleScope::current_" (?
> > [EMAIL PROTECTED]@v8@@[EMAIL PROTECTED]@A)
>
> > Any help/advice is appreciated, I'm using the latest SVN code as of
> > the time on this post
--~--~---------~--~----~------------~-------~--~----~
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to