> (not sure if it was ever really there to begin with).
It's officially not supported, but they will take patches
> IDE we use (JetBrains CLion) doesn't allow building with the MS toolchain.
It uses cmake though, so you can always tell cmake to generate a build
config for VS.
> I've put
I've put together a quick guide and patches for getting v8 building for
MinGW, available here: https://github.com/cchamplin/v8-mingw-guide. If you
want to test it and let me know that would be great. If everything seems
functional with the code changes I'll work on clean up and getting them
lgtm3
сре, 11. мај 2016. у 14.38 Adam Klein је написао/ла:
> lgtm2
>
> On Wed, May 11, 2016 at 10:58 AM, Jochen Eisinger
> wrote:
>
>> lgtm1
>>
>> Daniel Ehrenberg schrieb am Mi., 11. Mai 2016,
>> 19:55:
>>
>>> Primary eng email
lgtm2
On Wed, May 11, 2016 at 10:58 AM, Jochen Eisinger
wrote:
> lgtm1
>
> Daniel Ehrenberg schrieb am Mi., 11. Mai 2016,
> 19:55:
>
>> Primary eng email
>> little...@chromium.org
>>
>> *Summary*
>> Remove most of V8's additional methods and
lgtm1
Daniel Ehrenberg schrieb am Mi., 11. Mai 2016,
19:55:
> Primary eng email
> little...@chromium.org
>
> *Summary*
> Remove most of V8's additional methods and properties in ECMA 402 (Intl),
> namely v8Parse, resolved and pattern.
>
> V8 bug:
Unfortunately no. I gave up and went with the vs build. I was happy to
be able to make it build with the actual 2015 tool chain so that was nice.
It defaults to the 2013 toolchain.
On Wednesday, May 11, 2016, Brendan Bates wrote:
> Hey Zac,
>
> I'm also trying to
Hey Zac,
I'm also trying to build on MinGW right now. I have successfully built on
MSVC2015 but would much prefer MinGW (as all of our other products run
under MinGW in Windows). I have had no luck thus far, have you been able
to successfully build yet? I personally haven't got very far...
Yes, if I'm reading the source correctly, it looks like "v8::Script::Run"
can include time spent on lazy compilation.
On Tue, May 10, 2016 at 6:46 PM, Borislav Stanimirov wrote:
> The time spent in v8::Script::Compile is not counted in the aforementioned
> blocks. There
Hello Jochen,
I tried caching the keys after creating them using ForApi(), and this is
somewhat faster.
Still, I see that the GetPrivate/SetPrivate API's are considerably slower
than their Get/Set counterparts.
What did you mean by maintaining a weak map? Can you please be more
specific?