Yoshiyuki Mineo
Yoshiyuki Mineo
I think `fetch v8` failed in your environment. Could you try the following steps and check if your environment can fetch v8? ``` git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git export PATH=`pwd`/depot_tools:"$PATH" fetch v8...
Sorry for very late reply. v8eval supports V8 engine itself and JavaScript built-in functions. So it does not support Node functions.
Certainly there is no need to reject remote debugger connections. I think it's another simple solution to replace `127.0.0.1` with `0.0.0.0`. What do you think?
v8eval never run the debug server until `EnableDebugger` is called. I will replace `127.0.0.1` with `0.0.0.0` and write it explicitly in the docs.
Sorry for very late reply. Please see `cmake: command not found` in your log. v8eval requires cmake.
@Alemalakra I think you failed to build V8 because of the old v8eval version. Could you try the latest v8eval 0.3.0 ?
Sorry for very late reply. Please see `swig: command not found` in your log. v8eval requires swig and a recent version of Clang that can build V8.
v8eval depends on V8 toolchain. The message from V8 toolchain tells you that Ubuntu 19.04 is not supported.
Sorry for the late reply. As of now, v8eval supports Mac, Linux and other xNIX. v8eval uses a Bourne Shell script and it does not work on Windows natively. But...
v8eval builds V8 when installed, so that it takes for a while (for example, several tens of minutes). The build time depends on the performance of your local machine (CPU...