Re: [v8-users] Re: v8 static library on windows gives linker errors

2018-10-08 Thread Jakob Kummerow
> > The v8_monolith.lib is unbelievably huge (nearly a gig) > That's probably mostly debug info. Try Release mode ("is_debug = false"). -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the

Re: [v8-users] Re: v8 static library on windows gives linker errors

2018-10-08 Thread Mike Moening
Did a little more googling and found this option for the args.gn file: v8_monolithic = true is_debug = true is_clang = false v8_target_cpu = "x64" target_cpu = "x64" v8_enable_backtrace = true v8_enable_slow_dchecks = true v8_optimized_debug = false is_component_build = false v8_static_library =

Re: [v8-users] Re: v8 static library on windows gives linker errors

2018-10-08 Thread Mike Moening
I like the idea of a single library. I tried the following based on the instructions I saw: ninja -C out.gn/x64.debug v8_monolith but got this error: ninja: Entering directory `out.gn/x64.debug' ninja: error: unknown target 'v8_monolith' > >> -- -- v8-users mailing list

Re: [v8-users] Re: v8 static library on windows gives linker errors

2018-10-08 Thread Jakob Kummerow
The set of required libraries should be: v8_base v8_snapshot v8_libbase v8_libplatform v8_libsampler Does that work? As a simpler alternative, the instructions recommend to use the "v8_monolith" target, which should

[v8-users] Re: v8 static library on windows gives linker errors

2018-10-08 Thread Mike Moening
I tried linking in the v8_init.lib file to my project. The same error still exists but under another library? 1>v8_init.lib(setup-isolate-full.obj) : error LNK2019: unresolved external symbol "protected: static void __cdecl v8::internal::SetupIsolateDelegate::SetupBuiltinsInternal(class