Have you switched you project to use the v8.h include file from trunk as well and rebuild your project? We do not provide binary compatibility between different versions of V8. E.g `v8::Value::IsString() const' was marked as inline in v8.h at some point and therefore there should be no references to it from you projects object files. Regarding tags we have branches for version 1.1 (used in Chrome 2.0) and version 1.2 (used in Chrome 3.0 beta). Current trunk is 1.3 which is currently used in the Chromium project. I suggest that you try to keep you project using trunk as that will give you the benefit of all the latest changes to V8. When a new version is pushed to trunk (from the bleeding_edge branch where actual development takes place) the Chromium project is almost always updated immediately to ensure compatibility and stability.
Regards, Søren On Fri, Sep 4, 2009 at 08:40, kripken <[email protected]> wrote: > > I have a project that has been using V8 1.0 so far, and just now I > tried the latest trunk, but get strange linking errors. V8 itself > builds ok, but when I link it against my project, I get several > errors, > > undefined reference to `v8::Value::IsString() const' > undefined reference to `v8::Function::Cast(v8::Value*)' > undefined reference to `v8::V8::DisposeGlobal(void**)' > undefined reference to `v8::V8::GlobalizeReference(void**)' > collect2: ld returned 1 exit status > > I'm not sure what's causing these. V8 1.0 links (and runs fine) > against my exact same code without issue. This happens both when > compiled as release and debug. > > Is this an issue with trunk not currently building for anyone, or is > there some strange problem with my setup? Thanks in advance. > > - Kripken > > P.S. Should I be using a tag instead? The last tag seems to be 1.1, > but trunk says it is 1.3.9. > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
