Dear ArangoDB team,
while working with the dev branch of ArangoDB I noticed that the upcoming version 3.9 will include the updated version of RocksDB (6.26). Although not necessary, I was wondering if you are also considering to update the V8, especially since it has a very rapid release cycle and older versions fall out of support fast. With minor modifications to the code (arangodb), I was able to migrate to version 9.4.146.24 on Ubuntu 20.04. However, the new versions of V8 are usually built with Google’s depot tools (gn or gm) instead of gyp which also requires the adaptation of the CMake file to the new build system. When replacing some deprecated functions/methods with their successors the build passes all tests executed with arangodbtests. While I do not have the possibilities to test on Windows, Mac and ARM it seems feasible for someone more familiar with these platforms to easily add the necessary changes. One problem I encountered was that V8 is typically built with top of the branch Clang and linked against its libc++ which breaks the static linking with the native libc++ or libstdc++. However, when compiling ArangoDB with gcc and linking V8 against the native libstdc++ (configurable via build params) everything seems to work. I am not sure what would happen on platforms like Mac where Clang/LLVM is the native toolchain. While the changes I made do not have stable release quality, I would be happy to share them as inspiration in case you would be interested. Thank you for your time and effort. -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/arangodb/f291dea0-44de-48b9-be21-e39d82694e12n%40googlegroups.com.
