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
Unfortunately vcpkg has moved LuaJIT headers to a luajit/ subdirectory (microsoft/vcpkg#5863). It is my understanding that this means that sol2 can not be used with LuaJIT if both are installed via vcpkg, because soll will always look for lua.h, is that correct?
I would propose to provide a way to customize the include directory with something like SOL_LUA_INCLUDE_PATH_BASE or something that will be prepended to the header names before inclusion. Like this:
Unfortunately vcpkg has moved LuaJIT headers to a
luajit/
subdirectory (microsoft/vcpkg#5863). It is my understanding that this means that sol2 can not be used with LuaJIT if both are installed via vcpkg, because soll will always look forlua.h
, is that correct?I would propose to provide a way to customize the include directory with something like
SOL_LUA_INCLUDE_PATH_BASE
or something that will be prepended to the header names before inclusion. Like this:This would require some ugly macro magic to build the correct include paths and probably make the includes a bit less readable.
Alternatively one could provide
SOL_INCLUDE_PATH_LUA
,SOL_INCLUDE_PATH_LAUXLIB
andSOL_INCLUDE_PATH_LUALIB
respectively to specify the paths directly.Then I would just be able to do this:
This way sol2 will be robust against any future changes in vcpkg package layouts as well.
The text was updated successfully, but these errors were encountered: