I am only distributing the release version of my app. Can you give more specific explanation of how dependency walker will help?
Thanks, Jeff On Oct 13, 8:16 pm, Pete Gontier <[EMAIL PROTECTED]> wrote: > If you are distributing a debug build of your app, it depends on the > debug builds of the shared libraries for the C/C++ runtime, and the > only way to get those libraries is to have the appropriate version of > Visual Studio installed. Happily, the Express flavors are enough. > Alternatively, distribute the release build of your app. > > If you are not distributing a debug build of your app, and people > still have problems, then you probably want to play around with > Dependency Walker and see if you can figure out why. If nothing jumps > out at you, then consider finding a way for the people experiencing > the problems to do the same. If there is a problem loading your app, > Dependency Walker will make it glaringly obvious, and a screen shot > should be enough. > > Pete Gontier <http://pete.gontier.org/> > > On Oct 13, 2008, at 1:29 PM, codedread wrote: > > > > > Sorry to resurrect this, but I have a question surrounding this exact > > topic: > > > - I have a rather large code base that heavily uses SDL (http:// > >www.libsdl.org/faq.php?action=listentries&category=4#43) which must > > be /MD (Multithreaded DLL) > > - I have integrated V8 into my code (the DLL is apparently built > > using /MT as you state) > > - I am using Visual Studio 2005 SP1 > > - I have included the distributable runtime files (msvcm80.dll, > > msvcp80.dll, msvcr80.dll) > > > I can run my app just fine on my computer. In fact, it seems I can > > run the file on any computer installed with VS 2005. > > > However, since integrating V8, people without VC 2005 cannot run my > > executable program, they get a "The application failed to initialize > > properly" dialog and then it quits. I have tried to integrate v8 as a > > static library or as a shared library (/DUSING_V8_SHARED) with the > > same result. Again, I get no errors upon compiling or linking, it's > > only at the client end that the error occurs. > > > 1) Are there other DLLs that I need to include with my distributable? > > 2) Is there a way to build V8 with /MD so that all are consistent? I > > tried to do this and I get 'inconsistent dll linkage' errors > > surrounding strtod/gay_strtod... > > > I realliy appreciate any clues you can give me. > > > Thanks, > > Jeff > > > On Oct 2, 2:51 am, "Søren Gjesse" <[EMAIL PROTECTED]> wrote: > >> In the V8 build we have decided to use /MT (and /MTd) in order to > >> minimize > >> the external dependencies. One could argue that if building a DLL > >> the DLL > >> itself should use DLL's as much as possible, or there should be > >> another > >> option to determin whether the V8 DLL should use the static or > >> dynamic CRT > >> library. I don't think mixing /MT and /MD is a problem here as we > >> are not > >> using CRT library stuff across the V8 API boundary. Off cause > >> mixing /MT and > >> /MD will give you two copies of the CRT library in your application. > >> Regards, > >> Søren > > >> On Fri, Sep 26, 2008 at 1:57 PM, Garry <[EMAIL PROTECTED]> wrote: > > >>> 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 -~----------~----~----~----~------~----~------~--~---
