You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment our build system happily searches for LuaJIT and uses it when for example no other Lua installation is found or works with Luabind. This is dangerous since LuaJIT is not a first-class citizen in OSRM: we never test with it, don't run any setups with it and users are reporting crashes on various platforms and setups. Let's rip it out for good, since Lua/Luabind is already a pain in itself.
Instead of justifying a (potential?) performance improvement during extraction using LuaJIT we rather should explore for example not context switching between Lua and C++ on every Node / Way: #1777.
no longer try to use it in CMakeLists.txt
do not test if Luabind compiles with it in cmake/check_luabind.cmake
remove CMake module searching for Luajit cmake/FindLuaJIT.cmake
The text was updated successfully, but these errors were encountered:
At the moment our build system happily searches for LuaJIT and uses it when for example no other Lua installation is found or works with Luabind. This is dangerous since LuaJIT is not a first-class citizen in OSRM: we never test with it, don't run any setups with it and users are reporting crashes on various platforms and setups. Let's rip it out for good, since Lua/Luabind is already a pain in itself.
Instead of justifying a (potential?) performance improvement during extraction using LuaJIT we rather should explore for example not context switching between Lua and C++ on every Node / Way: #1777.
CMakeLists.txt
cmake/check_luabind.cmake
cmake/FindLuaJIT.cmake
The text was updated successfully, but these errors were encountered: