Re: [v8-users] Re: Different object files generated when cross compiling V8 7.3 for Android ARM (vs V8 7.2)

I'm facing the same issue. I built v8 for Android, and when linking `libv8_monolith.a` in my app using NDK, there are link errors. The app and the other third-party libs use the NDK libc++ expecting the `std::__ndk1` namespace, but v8 is expecting `std::__1`. I couldn't find a way to tell the v

Re: [v8-users] Re: Different object files generated when cross compiling V8 7.3 for Android ARM (vs V8 7.2)

rmation is outdated if using a recent version of v8. On Tue, Jun 16, 2020, at 2:52 PM, Jean-Claude Monnin wrote: > I'm facing the same issue. I built v8 for Android, and when linking > `libv8_monolith.a` in my app using NDK, there are link errors. The app and > the other third-par

[v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

Hi, On windows, the v8 version 11.5 build fails when generating the snapshot with following error: C:/Users/jean-claude/Documents/src/google/depot_tools/bootstrap-2@3_8_10_chromium_26_bin/python3/bin/python3.exe ../../tools/run.py ./mksnapshot --turbo_instruction_scheduling --target_os=win --t

Re: [v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

test coverage for `use_custom_libcxx=false`, this > mode is only supported on a best-effort basis. > > For debugging: a backtrace and symbols would be useful. Does running > `mksnapshot` in a debugger give more infos? Also, a bisect to find the > culprit change would be very

Re: [v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

t;> >> For debugging: a backtrace and symbols would be useful. Does running >> `mksnapshot` in a debugger give more infos? Also, a bisect to find the >> culprit change would be very helpful. >> >> On Thu, Aug 3, 2023 at 6:54 PM Jean-Claude Monnin

Re: [v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

ot sure how to fix/work around. On Wed, Aug 9, 2023, at 8:03 AM, Jakob Gruber wrote: > > > On Tue, Aug 8, 2023 at 3:20 PM Jean-Claude Monnin > wrote: >> __ >> Hi Jakob, >> >> Thanks for your reply. >> It looks like using Microsoft's C++ librar

Re: [v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

The output is > Test1 before init_func > called CallOnceFake1 lambda > Test1 after init_func > Test2 before init_func > called TestFunction > Test2 after init_func > Test2 before init_func The call to `Test2` with a lambda crashes On Wed, Aug 9, 2023, at 10:32 AM, Jakob Gru

Re: [v8-users] mksnapshot fails on windows with is_official_build = true, is_component_build = true, use_custom_libcxx = false

trying to > build a minimal repro (without V8). I'd still like to understand if this is a > bug in V8 or in the MSVC stdlib. > > On Wed, Aug 9, 2023 at 6:05 PM Jean-Claude Monnin > wrote: >> __ >> Hi Jakob, >> >> Sorry, I should have looked at the co

Re: [v8-users] Re: [v8-dev] MSVC will be unsupported after V8 version 13.0

Hi Hannes, Just a clarification: Does that mean only MSVC the compiler isn't supported anymore, but the Microsoft C++ Standard Library still works [1]? As you said, clang-cl is ABI compatible with MSVC, so I don't care which compiler is used to compiled v8, as long as I can link v8 with other c

Re: [v8-users] Re: [v8-dev] MSVC will be unsupported after V8 version 13.0

ld be private to V8 and Microsoft standard library could be used > for the rest. > > Cheers, > Hannes > > On Tue, Jun 18, 2024 at 9:41 AM Jean-Claude Monnin > wrote: >> __ >> Hi Hannes, >> >> Just a clarification: Does that mean only MSVC the comp