- is_clang=false
>>>>>>> is_component_build=true*
>>>>>>>
>>>>>>> Run the build, which should complete without error:
>>>>>>>
>>>>>>> * ninja -C out.gn/msvc <http://o
gt;>>>> <http://out.gn/msvc>*
>>>>>>
>>>>>> You should find the resulting v8.dll, along with supporting dlls and
>>>>>> .lib files, in the .\out.gn\msvc directory.
>>>>>>
>>>>>> I haven't tes
gt;>>>>> You should find the resulting v8.dll, along with supporting dlls and
>>>>>> .lib files, in the .\out.gn\msvc directory.
>>>>>>
>>>>>> I haven't tested much beyond running the tests and doing a few ad-hoc
>>>>
>>> D8 experiments, and obviously this is unsupported/untested upstream
>>>>> (where
>>>>> the are no bots building/testing/fuzzing this configuration).
>>>>>
>>>>> I'll tidy this up, open a CL, and see if this is something w
gt;>>> fixes,
>>>> is would then be beholden on us (the V8 community) to keep it working.
>>>> (Personally, it seems to me like the only long-term sustainable solution
>>>> for cross-compiler support is a C-based API, similar to N-API for Node.js,
>>> (Personally, it seems to me like the only long-term sustainable solution
>>> for cross-compiler support is a C-based API, similar to N-API for Node.js,
>>> but I doubt there's much appetite for this currently).
>>>
>>> - Bill
>>>
>>>
>>> On Friday, Decem
I, similar to N-API for Node.js,
>> but I doubt there's much appetite for this currently).
>>
>> - Bill
>>
>>
>> On Friday, December 20, 2019 at 10:29:07 AM UTC-8, Ivan Pizhenko wrote:
>>>
>>> Oh, that’s great. Thank you. I will try to apply similar
8.279.23, since I am allowed to use only “stable” versions of V8.
>>
>> - Ivan
>>
>>
>>
>>
>>
>> *From: *'Bill Ticehurst' via v8-users
>> *Sent: *Friday, December 20, 2019 20:02
>> *To: *v8-users
>> *Subject: *[v8-users] Re:
;mailto:ivan.pizhe...@genesys.com>
Sent: Friday, December 20, 2019 20:29
To: v8-users@googlegroups.com<mailto:v8-users@googlegroups.com>
Subject: RE: [v8-users] Re: Building v8 shared library on windows
Oh, that’s great. Thank you. I will try to apply similar patch locally to the
7.8.279.
cember 20, 2019 at 10:29:07 AM UTC-8, Ivan Pizhenko wrote:
>>
>> Oh, that’s great. Thank you. I will try to apply similar patch locally to
>> the 7.8.279.23, since I am allowed to use only “stable” versions of V8.
>>
>> - Ivan
>>
>>
>>
>>
>>
>>
rsions of V8.
>
> - Ivan
>
>
>
>
>
> *From: *'Bill Ticehurst' via v8-users
> *Sent: *Friday, December 20, 2019 20:02
> *To: *v8-users
> *Subject: *[v8-users] Re: Building v8 shared library on windows
>
>
>
> FWIW: I played around with the last ni
There are a couple of things I don't understand:
-How can I use V8 with VS2019, if working DLLs can't be obtained?
-Will the MSVC way ever be fixed?
I cannot use precompiled DLLs if I don't know if I will be able to update
them to a newer version of V8, that wouldn't be sustainable.
Thank you
:v8-users@googlegroups.com>
Subject: [v8-users] Re: Building v8 shared library on windows
FWIW: I played around with the last night for a couple hours and got a release
build working using a "component build" and MSVC. It was mostly moving some
inline functions and adding some V8_EXP
-users<mailto:v8-users@googlegroups.com>
Subject: Re: [v8-users] Re: Building v8 shared library on windows
Just the header file for the public V8 API
(https://chromium.googlesource.com/v8/v8.git/+/refs/heads/master/include/v8.h#18<https://chromium.googlesource.com/v8/v8.git/+/refs/heads/mast
FWIW: I played around with the last night for a couple hours and got a
release build working using a "component build" and MSVC. It was mostly
moving some inline functions and adding some V8_EXPORT_PRIVATE statements
(which effectively add the "__declspec(dllexport)" statements to expose
lopers to keep all
>> public V8 APIs w/o any STL stuff for the sake of better integration with
>> different compilers, which with very high probability have different STL
>> implementations than libc++.
>>
>> - Ivan
>>
>>
>>
>>
>>
>> *
cember 18, 2019 20:22
> *To: *v8-users
> *Subject: *[v8-users] Re: Building v8 shared library on windows
>
>
>
> I believe this is still mostly correct - (some filenames might be out of
> date, but should give you a general starting point). If you're already
> building V8 suc
> *Sent: *Wednesday, December 18, 2019 20:22
> *To: *v8-users
> *Subject: *[v8-users] Re: Building v8 shared library on windows
>
>
>
> I believe this is still mostly correct - (some filenames might be out of
> date, but should give you a general starting point). I
<mailto:v8-users@googlegroups.com>
Sent: Wednesday, December 18, 2019 20:22
To: v8-users<mailto:v8-users@googlegroups.com>
Subject: [v8-users] Re: Building v8 shared library on windows
I believe this is still mostly correct - (some filenames might be out of date,
but should give you a gene
I believe this is still mostly correct - (some filenames might be out of
date, but should give you a general starting point). If you're already
building V8 successfully with MSVC, you should be able to skip down to the
"Embedding V8 into a custom application" part.
I'm not clear on what is needed to fix this. The bug has been open quite a
while (see https://bugs.chromium.org/p/v8/issues/detail?id=8791).
On Tuesday, December 17, 2019 at 12:44:14 PM UTC-8, Ivan Pizhenko wrote:
>
> Hi Bill, so what needs to be fixed to get DLL build (i.e.
>
Ok Bill
Then I'll build it statically with "is_component_build = false". I don't
really need them to be dynamic, I just need them to work.
What file extension should I look for? .lib?
Thank you
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
Hi Bill, so what needs to be fixed to get DLL build (i.e.
is_component_build=true) built successfully with MSVC compiler?
I've recently run into the same linking issue with DLL build compiled using
clang. And to say truth, it's weird that DLL build works only with clang.
p.s. I cannot use
The v8 libraries from nuget can be used well with VC2017. Thats all i know.
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsubscribe from this
To be clear, NuGet is a Microsoft run package manager, but "Microsoft"
doesn't offer any pre-built V8 binaries. A user account named "pmed"
created/uploaded that package, not a Microsoft account.
If you are building V8 in a default manner with Clang as it appears, then
you can't link it with a
Note that Microsoft also offers prebuild verrions of v8 via the package
manager or direct to download.
I.e. https://www.nuget.org/packages/v8-v140-x64/ click on "Download" at the
right and rename the archive to zip. Works well for me.
--
--
v8-users mailing list
v8-users@googlegroups.com
>
> Nagendra, what do you mean with "using libc++ insead of stdlibc++ when
> using the host_cpu toolchain"? I don't get it.
>
Right now I'll compile with "is_clang = true" and
"use_custom_libcxx_for_host = true".
Thank you both.
--
--
v8-users mailing list
v8-users@googlegroups.com
Ok
I'm still going to compile with "is_clang = true", but I'll also add
Nagendra's "use_custom_libcxx_for_host = true".
Don't expect me to disappear from this platform.
Thank you very much
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You
> I'll try compiling with "is_clang = true"
Shouldn't hurt, although my suspicion is since you didn't override it, it
defaulted to true, due to these lines from "build/config/BUILDCONFIG.gn":
is_clang = current_os != "linux" ||
(current_cpu != "s390x" && current_cpu != "s390" &&
OP should also take a look at this thread
https://groups.google.com/forum/#!topic/v8-users/Jb1VSouy2Z0
I'm facing the same linking issue on using v8 shared libs on CentOS 8
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this
While you wait for someone *much* more knowledgeable to reply... :-)
I'm not brave enough to build on Windows, but presumably many things are
similar.
> I'm following the guide.
More than one guide (or parts of guide) to follow! :-) Maybe you followed
this one: https://v8.dev/docs/embed
In
Are you building with MSVC or Clang? The "component" build of V8 has some
issues with MSVC, but I believe should just work if using Clang.
Note: "component" build means a DLL build. Check that "is_component_build =
true" in your output folder's args.gn file, and then you should see v8*.dll
32 matches
Mail list logo
