-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rockspec build with cmake and -G Ninja flag failed #1476
Comments
Spotted the potential error: fs.execute_string("cmake -H. -Bbuild.luarocks -G\"MinGW Makefiles\" -DCMAKE=\"cmake -S . -B build -G Ninja ^\" -DCMAKE_TOOLCHAIN_FILE=\"C:/vcpkg/scripts/buildsystems/vcpkg.cmake\" -DCMAKE_BUILD_TYPE=\"Release\" -DCMAKE_CXX_FLAGS=\"\"/D_WIN32_WINNT=0x0601 /DWINVER=0x0601 /DWIN32 /D_WINDOWS /EHsc /MD\"\" -DLUAJIT_COMPILED=\"D:/a/Noita-Synchronise-Expansive-Worlds/Noita-Synchronise-Expansive-Worlds/LuaJIT/LuaJIT-2.0.4\" -DNSEW_EXTERNAL_MAP=\"OFF\" -DNSEW_PREBUILT_DOCS_DIR=\"D:/a/Noita-Synchronise-Expansive-Worlds/Noita-Synchronise-Expansive-Worlds/doc\" -DVCPKG_TARGET_TRIPLET=\"x86-windows-static\"") |
luarocks config:
There you can see |
I fixed it by adding lua_interpreter = "luajit.exe"
cmake_generator = "Ninja"
variables = {
-- your local absolute paths
} Is there a better way to change the cmake named generator? In addition, I had to update MSYS2 to use cmake version 3.22:
Use this to update your MSYS2! |
|
Closed, because of lack of knowledge. Doesn't seem to be a bug or issue, I think. |
Please read the following before submitting:
chat-room.
tracker before submitting.
Please fill out the following:
Platform:
LuaRocks version:
luarocks --version
: 3.9.1 standalone with project 'nsew'Configuration file:
the minimal configuration to reproduce.
--verbose
flag.I am trying to build a forked repo with luarocks, but it seems that the cmake flags aren't recognised.
Any hint what I am doing wrong, would be nice.
I already found this, but didn't help: #509 (comment)
Edit: Added verbose logging of build command.
The text was updated successfully, but these errors were encountered: