Re: [v8-users] Re: Building v8 shared library on windows

2020-04-01 Thread 'Bill Ticehurst' via v8-users
nfiguration). >>>> >>>> I'll tidy this up, open a CL, and see if this is something we can get >>>> upstreamed, as several folks seem to want this option. Assuming V8/Google >>>> doesn't want to run bots for this configuration but is happy to take &

[v8-users] Re: error LNK2001: unresolved external symbol v8::platform::NewDefaultPlatform

2020-02-19 Thread 'Bill Ticehurst' via v8-users
Seeing as you state the error message is in VS2019, I'm assuming you are trying to use these libraries once built from a Visual Studio/MSVC project? If so, the issue may be that you are building V8 with one toolchain and standard library (i.e. clang & libc++), and trying to consume with another

[v8-users] Re: Building v8 shared library on windows

2019-12-20 Thread 'Bill Ticehurst' via v8-users
FWIW: I played around with the last night for a couple hours and got a release build working using a "component build" and MSVC. It was mostly moving some inline functions and adding some V8_EXPORT_PRIVATE statements (which effectively add the "__declspec(dllexport)" statements to expose

Re: [v8-users] Re: Building v8 shared library on windows

2019-12-19 Thread 'Bill Ticehurst' via v8-users
lopers to keep all >> public V8 APIs w/o any STL stuff for the sake of better integration with >> different compilers, which with very high probability have different STL >> implementations than libc++. >> >> - Ivan >> >> >> >> >> >> *

[v8-users] Re: Building v8 shared library on windows

2019-12-18 Thread 'Bill Ticehurst' via v8-users
I believe this is still mostly correct - (some filenames might be out of date, but should give you a general starting point). If you're already building V8 successfully with MSVC, you should be able to skip down to the "Embedding V8 into a custom application" part.

[v8-users] Re: Building v8 shared library on windows

2019-12-18 Thread 'Bill Ticehurst' via v8-users
I'm not clear on what is needed to fix this. The bug has been open quite a while (see https://bugs.chromium.org/p/v8/issues/detail?id=8791). On Tuesday, December 17, 2019 at 12:44:14 PM UTC-8, Ivan Pizhenko wrote: > > Hi Bill, so what needs to be fixed to get DLL build (i.e. >

[v8-users] Re: Building v8 shared library on windows

2019-12-17 Thread 'Bill Ticehurst' via v8-users
To be clear, NuGet is a Microsoft run package manager, but "Microsoft" doesn't offer any pre-built V8 binaries. A user account named "pmed" created/uploaded that package, not a Microsoft account. If you are building V8 in a default manner with Clang as it appears, then you can't link it with a

[v8-users] Re: Building v8 shared library on windows

2019-12-06 Thread 'Bill Ticehurst' via v8-users
Are you building with MSVC or Clang? The "component" build of V8 has some issues with MSVC, but I believe should just work if using Clang. Note: "component" build means a DLL build. Check that "is_component_build = true" in your output folder's args.gn file, and then you should see v8*.dll