Zeblote
Zeblote
Is there some way to query the OS _why_ it failed?
Nice! Would it be possible to pass that error all the way up so the program calling dir patch receives i.e. DIRPATCH_DISK_FULL? That way we can show the correct message...
Thanks! That looks like it will really help.
Oh! That's for building with gyp though, v8 wants to build with this new gn thing now... I'll see if it has similar options
I tried using similar gn settings, but it's not successful so far. The setting v8_enable_inspector doesn't actually exist in gyp or gn. ``` is_debug = false target_cpu = "x64" v8_use_snapshot...
Next try: ``` is_debug = false target_cpu = "x64" v8_use_snapshot = false v8_static_library = true is_component_build = false v8_enable_i18n_support = false treat_warnings_as_errors = false ``` I also to v8/build/config/win/BUILD.gn and...
I don't think it is, building v8 works fine. The problem only appears when trying to link it in your plugin.
Oh. I've added these 2 libs for 6.0, but it's still not linking properly. Now the number of errors is down to 2 though: ``` 2>Module.V8.cpp.obj : error LNK2019: unresolved...
I searched the entire v8 folder for enable_inspector and the setting doesn't exist. Maybe it has been renamed.
Ok, it seems to work if I also copy over `v8/out.gn/x64.release/obj/src/inspector/inspector.lib` and add `PublicAdditionalLibraries.Add("shlwapi.lib");` to `V8.Build.cs`. Is there any advantage to building with GN then? I only wanted to use...