you need to add the v8 directory to your include paths (not v8/include -
though having both is also fine).
And yes, you have to link against the .lib file, there is no dll support
for v8_libplatform (yet)
best
-jochen
On Wed, Sep 10, 2014 at 4:28 AM, James W contac...@jameswilkins.net wrote:
I compiled V8 successfully, and included libplatform.h in my host code
(in order to call v8::platform::CreateDefaultPlatform()). libplatform.h
now complains error C1083: Cannot open include file:
'\include/v8-platform.h': No such file or
directory \include\libplatform\libplatform.h. I can
Hey,
that's not true. API changes are documented here:
http://bit.ly/v8-api-changes and there was an PSA about this change a few
weeks ago and API changes are documented in the logs of each release.
However, if you chose to build from bleeding_edge or any other not yet
released version, you're
You need to initialize the platform, see e.g.
https://code.google.com/p/v8/source/browse/branches/bleeding_edge/samples/shell.cc#82.
No fancy locking etc. involved here, the platform is internally just a
global variable. Not nice, but OK for now...
--
--
v8-users mailing list
Note that you'll also need to link against the v8_libplatform library to
make this work
best
-jochen
On Fri, Sep 5, 2014 at 9:23 AM, Sven Panne svenpa...@chromium.org wrote:
You need to initialize the platform, see e.g.
Why is this not shown in the Google embedders guide?
-jw
(sent via iPhone)
On Sep 5, 2014, at 3:53 AM, Jochen Eisinger joc...@chromium.org wrote:
Note that you'll also need to link against the v8_libplatform library to make
this work
best
-jochen
On Fri, Sep 5, 2014 at 9:23 AM,
The philosophy seems to be that the code is always the most up to date
Documentation of v8. So questions about API and usage are best
answered by reading v8.h [0], and d8.cc [1] and/or samples (shell.cc
[2], process.cc [3], and lineprocessor.cc [4]), and/or the files in
src/.
[0]
Ok, thanks.
-jw
(sent via iPhone)
On Sep 5, 2014, at 1:17 PM, Louis Santillan lpsan...@gmail.com wrote:
The philosophy seems to be that the code is always the most up to date
Documentation of v8. So questions about API and usage are best
answered by reading v8.h [0], and d8.cc [1] and/or
Addition details: I'm using Visual Studio 2013, and compiled the source,
the resulting libraries of which I use with the V8.Net wrapper (on
codeplex). I run the following code before triggering the idle notification
call:
v8::Locker __lockScope(engine-Isolate());
v8::Isolate::Scope
