OK, I finally got v8 to work and the lib to a reasonable size. For the records, the lib file generated while creating the dll is the one to use. It is about 180 K in size. Then, one has to recompile the program that uses v8 with the preprocessor option USING_V8_SHARED and add the lib file to the project. Then, you need to ensure that v8.dll is in the working directory at startup.
On Wed, Jan 6, 2010 at 7:35 AM, Philippe Roy <[email protected]> wrote: > Thank you Stephan. You are a gentleman and I concur with your views on > documentation. I think that Google should show some leadership on such > issue. After all, their name is behind it... > > So far, the command... > > scons mode=release library=shared env="PATH:C:\Program Files\Microsoft > Visual Studio 9.0\VC\bin;C:\Program Files\Microsoft Visual Studio > 9.0\Common7\IDE;C:\Program Files\Microsoft Visual Studio > 9.0\Common7\Tools,INCLUDE:C:\Program Files\Microsoft Visual Studio > 9.0\VC\include;C:\Program Files\Microsoft > SDKs\Windows\v6.0A\Include,LIB:C:\Program Files\Microsoft Visual > Studio 9.0\VC\lib;C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib" > > ...build v8.lib (187K) and v8.dll (1.41MB) but results in these 2 > linking errors in the code: > > Error 1 error LNK2001: unresolved external symbol "public: static int > v8::internal::Internals::kJSObjectType" > (?kjsobjectt...@internals@inter...@v8@@2HA) JSObjectSupport.obj > DigitalConceptBuilder > Error 2 error LNK2001: unresolved external symbol "public: static int > v8::internal::Internals::kFirstNonstringType" > (?kfirstnonstringt...@internals@inter...@v8@@2HA) Predicate.obj > DigitalConceptBuilder > > I am wondering if a recent add by someone which may have forgotten to > update the build file may be the cause of that. > > Should I be able to get around these 2 linking errors, I would be in business. > > Thank you > > On Tue, Jan 5, 2010 at 11:45 PM, Stephan Beal <[email protected]> wrote: >> On Wed, Jan 6, 2010 at 5:26 AM, Philippe Roy <[email protected]> >> wrote: >>> >>> I agree with you the topic has been brought many times, but at no >>> point to my knowledge it is written clearly "Here's the solution". >> >> Good luck finding any such docs for v8. i, as a standalone developer, write >> more documentation for my projects than the v8 team can seem to conjure up >> for v8. It's not my intention to flame the developers, but documenting code >> is a fundamental part of writing the code (they go hand in hand, IMO), and >> for all of v8's technical merits, documentation is not one of v8's merits. >>> >>> And >>> by the solution, I mean here's the scons command for Visual Studio >>> 2008 that will build you the library file that is reasonable in size. >> >> i don't use Windows (except to play Starwars Battlefront), so i can't help >> you out with that - i can only say that i've seen it brought up on this list >> before. >> >>> >>> Come on guys, I know someone has the solution... Throw it at me so >>> that I can go back to my 3 kids and play with them... >> >> i feel for you - i've spent hundreds of hours hacking on v8-based code, and >> many dozens of those hours have been spent trying to figure out how v8 >> really works (i.e. painful trial and error), since so much of the >> documentation is either missing or so minimal as to be useless. (i'm still >> wondering what API docs like "starts preemption" are trying to tell me.) >> Adequately documented software projects (libQt comes to mind) are >> unfortunately few and far between. >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> >> -- >> 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
