V8 compilation without custom libcxx

[Renato]

Hi,

I was updating an old V8 app to the latest API but I was having some linker errors (VS2019) related with this call:

std::unique_ptr<v8::Platform> platform = v8::platform::NewDefaultPlatform()

I found that now V8 uses a custom libcxx that I really don't want to propagate to my app so i tried to disable it... without success.

My V8 compile settings are: 

is_debug=false

is_component_build = true

target_cpu = "x64"

v8_enable_i18n_support=false

use_lld = false

v8_use_external_startup_data = false

use_glib=false 

use_custom_libcxx=false

use_prebuilt_instrumented_libraries=false

is_clang=false

v8_enable_embedded_builtins=false

use_locally_built_instrumented_libraries=false

v8_use_snapshot=true

To be able to get v8.dll, v8_libplatform.dll and v8_libbase.dll not depending of the new custom libcxx I had to checkout the tag 7.5.168.... none of the next versions works. 

Is there a new setting that I have to use with the newest tags to compile a v8.dll that doesn't depends on the custom libcxx?

thanks

[Cvetan Stefanovski]

Hello,

I have the same problem embedding V8 (7.5.288.23) into my Android application. I tried to get rid of that custom libcxx to no avail. Next that I want to try is to link my JNI <> V8 bridge library against the same libcxx that V8 libs link to.

Bump. Any of the devs having something to add?

[Jakob Gruber]

On Tue, Jul 2, 2019 at 2:17 AM Cvetan Stefanovski <cve...@gmail.com> wrote:

Hello,

I have the same problem embedding V8 (7.5.288.23) into my Android application. I tried to get rid of that custom libcxx to no avail. Next that I want to try is to link my JNI <> V8 bridge library against the same libcxx that V8 libs link to.

Bump. Any of the devs having something to add?

I'm not sure what you mean by 'tried to get rid ... to no avail'. The `use_custom_libcxx = false` flag should disable the custom libcxx and use the system library instead. Are you running into compile errors? Link errors? If so, please open a bug for this at crbug.com/v8/new.

See https://crbug.com/v8/9150#c2 for a bit more information on use_custom_libcxx.

 

On Tuesday, 18 June 2019 00:54:56 UTC+3, Renato wrote:

Hi,

I was updating an old V8 app to the latest API but I was having some linker errors (VS2019) related with this call:

std::unique_ptr<v8::Platform> platform = v8::platform::NewDefaultPlatform()

I found that now V8 uses a custom libcxx that I really don't want to propagate to my app so i tried to disable it... without success.

My V8 compile settings are: 

is_debug=false

is_component_build = true

target_cpu = "x64"

v8_enable_i18n_support=false

use_lld = false

v8_use_external_startup_data = false

use_glib=false 

use_custom_libcxx=false

use_prebuilt_instrumented_libraries=false

is_clang=false

v8_enable_embedded_builtins=false

use_locally_built_instrumented_libraries=false

v8_use_snapshot=true

To be able to get v8.dll, v8_libplatform.dll and v8_libbase.dll not depending of the new custom libcxx I had to checkout the tag 7.5.168.... none of the next versions works. 

Is there a new setting that I have to use with the newest tags to compile a v8.dll that doesn't depends on the custom libcxx?

thanks

--
--
v8-users mailing list
v8-u...@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 group and stop receiving emails from it, send an email to v8-users+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/d8805ef0-e078-46ad-a7cf-f6b3df4c5fc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.