Thanks for the reply Jochen,
How do I specify the msvs gyp generator?
On Wednesday, 21 September 2016 10:54:39 UTC+2, Jochen Eisinger wrote:
>
> If you want to build with MSVS, you need the msvs gyp generator.
> msvs-ninja only supports browsing the project, not building it
>
> On Tue, Sep 20,
On Wed, Sep 21, 2016 at 12:37 PM, kito wrote:
> Hi~
>
> I try to use the google's v8 in win32 application console Project of visual
> studio 2015. (For reference, I'm using Windows 10.)
>
> I will use the Accessor, trying to output the url of location.href.
>
>
> Sample code
If you want to build with MSVS, you need the msvs gyp generator. msvs-ninja
only supports browsing the project, not building it
On Tue, Sep 20, 2016 at 10:04 AM Pieter wrote:
>
> I have been struggling for a couple of days to get the correct
> incantations to get a
I filed https://bugs.chromium.org/p/v8/issues/detail?id=5412 as feature
request
On Wed, Sep 21, 2016 at 10:50 AM Jochen Eisinger
wrote:
> libplatform currently does not support dynamic linking.
>
> On Tue, Sep 20, 2016 at 7:43 PM Andre Cunha
>
libplatform currently does not support dynamic linking.
On Tue, Sep 20, 2016 at 7:43 PM Andre Cunha
wrote:
> Hello,
>
> I'm trying to dynamically load libplatform in an application I'm writing.
> I searched through the available gn options, but I couldn't find an
Okay. I'll try to link statically, then.
Thank you!
Andre
On Wednesday, September 21, 2016 at 5:52:12 AM UTC-3, Jochen Eisinger wrote:
>
> I filed https://bugs.chromium.org/p/v8/issues/detail?id=5412 as feature
> request
>
> On Wed, Sep 21, 2016 at 10:50 AM Jochen Eisinger
That'd be with
set GYP_GENERATORS=msvs
But I'm afraid we dropped official support for this a while back.
Why not build with ninja? E.g. gyp_generator like you specified and then
build with:
ninja -C out\Release
on x64 platforms might require:
ninja -C out\Release_x64
On Wednesday, September
After I have managed to get the windows build of v8 going I have a single
unresolved symbol issue that I could use some help with.
unresolved external symbol "public: static class v8::Local __cdecl v8::Context::New(class v8::Isolate *,class
v8::ExtensionConfiguration *,class
On Wed, Sep 21, 2016 at 2:47 PM, Pieter wrote:
> After I have managed to get the windows build of v8 going I have a single
> unresolved symbol issue that I could use some help with.
>
> unresolved external symbol "public: static class v8::Local v8::Context> __cdecl
Thanks for the reply Ben,
This is odd as this very same code compiles fine on OSX and Ubuntu with the
same branch checked out?
On Wednesday, 21 September 2016 18:21:21 UTC+2, Ben Noordhuis wrote:
>
> On Wed, Sep 21, 2016 at 2:47 PM, Pieter > wrote:
> > After I have
I'm embedding v8 and trying to upgrade to v8 5.3-lkgr. After I built v8
using GYP with GYPFLAGS="-Dv8_use_external_startup_data=0
-Dcomponent=shared_library", I got the following files under
out/x64.release/obj.target/src/:
js2c.stamp libv8_nosnapshot.a
libv8_base.a
Embedding v8. Currently on 4.6.88, and in the process of upgrading to
5.3.lkgr.
When I do a pstack of my program embedding v8, some of the v8 frames show
up as ???. I wonder whether there's a build flag I could use to enable the
full stack trace of v8 frames.
Please advise.
Thanks.
--
Trying to build v8 5.3-lkgr with gn for embedding use.
When I build with GYP, I need to set "-Dv8_use_external_startup_data=0".
Is there an equivalent setting flag for gn?
Also if I build with gn and I need to link with libv8_libplatform.a,
libv8_libbase.a etc, is there a flag to generate
Hi all,
I am trying in the last few days to build V8 for Android. I am using Ubuntu
64bit as the build machine. After a lot of tries I was able to make ninja
to start the build but after compiling few hundreds of files I get the
following linking error
*unrecognised emulation mode:
14 matches
Mail list logo