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
I just added luajit to vcpkg.json and tried to link it to my CMakeProject, however as it was with libwebm too, it does not create LuaJITConfig.cmake or luajit-config.cmake in the share folder, so I can't use it with my project.
Failure logs
-- Found Boost: C:/boost (found version "1.85.0")
CMake Error at C:/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
Could not find a package configuration file provided by "LuaJIT" with any
of the following names:
LuaJITConfig.cmake
luajit-config.cmake
Add the installation prefix of "LuaJIT" to CMAKE_PREFIX_PATH or set
"LuaJIT_DIR" to a directory containing one of the above files. If "LuaJIT"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
CMakeLists.txt:11 (find_package)
-- Configuring incomplete, errors occurred!
Additional context
No response
The text was updated successfully, but these errors were encountered:
@d1str4ught Currently vcpkg does not provide the cmake usage provided by luajit. You can use MSbuild to use luajit by running the command ./vcpkg integrate install
Operating system
Windows 11
Compiler
MSVC 2022
Steps to reproduce the behavior
Failure logs
-- Found Boost: C:/boost (found version "1.85.0")
CMake Error at C:/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
Could not find a package configuration file provided by "LuaJIT" with any
of the following names:
Add the installation prefix of "LuaJIT" to CMAKE_PREFIX_PATH or set
"LuaJIT_DIR" to a directory containing one of the above files. If "LuaJIT"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
CMakeLists.txt:11 (find_package)
-- Configuring incomplete, errors occurred!
Additional context
No response
The text was updated successfully, but these errors were encountered: