fix: do not define _LIBCPP_ABI_NAMESPACE=Cr for all native modules (#34932)
This define is only needed when linking against Chromiums libc++ which we currently do not ship / expose the symbols of. We probably should make those symbols visible and actually ensure that electron-rebuild et. al link against our libc++ instead of the system libc++ but for now this fixes compilation issues on macOS where the default system clang links to the system libc++ which does not (obviously) use the Chromium ABI namespace. For our nan tests which do link against Chromiums libc++ we define the ABI namespace in the spec runner.
This commit is contained in:
parent
9d23a624c1
commit
f1746c81c6
4 changed files with 3 additions and 24 deletions
|
@ -43,6 +43,5 @@ macos_avoid_posix_spawnp_cwd_bug_3597.patch
|
|||
src_update_importmoduledynamically.patch
|
||||
fix_add_v8_enable_reverse_jsargs_defines_in_common_gypi.patch
|
||||
json_parse_errors_made_user-friendly.patch
|
||||
build_define_libcpp_abi_namespace_as_cr_to_align_with_chromium.patch
|
||||
support_v8_sandboxed_pointers.patch
|
||||
build_ensure_v8_pointer_compression_sandbox_is_enabled_on_64bit.patch
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue