- 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
: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
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
17 matches
Mail list logo
