Updates:
Owner: [email protected]
Comment #4 on issue 2507 by [email protected]: Windows DLL Build Still
Broken in 3.16.7
http://code.google.com/p/v8/issues/detail?id=2507
Issue 2492 was a non-shared library build failure introduced in
bleeding_edge r13369 and fixed in r13381. The fix is still on bleeding_edge
(no reason why it would get lost) and also in current trunk.
Building on Windows with -Dcomponent=shared_library has been broken ever
since r13365 "Consistently use V8EXPORT on all classes and not on
individual methods".
Annotating the classes Handle, Local and Persistent with V8EXPORT reduces
the number of errors that are generated but does not make them go away
entirely. Apparently templatized classes can't be exported in this way
(which kinda makes sense). My guess is that the MSVC compiler tries to be
helpful by automatically exporting template classes that are needed and not
exporting those that aren't (in some other compilation unit), leading to
symbol clashes. Or something along those lines. I suspect we need to revert
to "inconsistent" usage of the V8EXPORT macro (some classes, some
functions) to appease the toolchain.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
