Linking to monolithic V8 build using in-tree libc++ causes linker errors on Windows

[Kasper Isager Dalsgarð]

Hi!

I'm seeing linker warnings and errors related to libc++ symbols when linking to a monolithic V8 build made using the in-tree libc++, i.e. `using_custom_libcxx = true`, on Windows. On both macOS and Linux I'm not seeing any issues and my executables are linked correctly.

Specifically, I'm seeing warnings like these...

```

lld-link : warning : <path>: locally defined symbol imported: public:
void __cdecl std::__Cr::__shared_weak_count::__release_weak(void) (defined in v8.lib(memory.obj))

```

...and errors like these:

```

lld-link : error : undefined symbol: __declspec(dllimport) public: void __cdecl std::__Cr::__shared_count::__add_shared(void)

```

Looking through the object library using `dumpbin /symbols` I'm indeed not seeing any of the symbols that the linker complains are missing so that part makes sense. There are a lot of `std::__Cr::*` symbols present though, so some of them make their way into the object library.

Any ideas on how I might solve this?

[Kasper Isager Dalsgarð]

Turns out I was missing a dependency from my executable to libc++ and so `_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS` wasn't propagated to the compile definitions.