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
Currently the lsp builds with gcc and libstdc++ no matter the env vars.
It is pretty important to me that binaries I use don't have a dependency on gcc_s and libstdc++.
I prefer building against libc++. Some may want use musl libc.
Using cmake would be better, even autotools or meson would do. But please ditch luamake
The whole project is deeply integrated with luamake — it isn’t just a simple switch of build systems. Moreover, luamake ultimately outputs Ninja files for compilation, so there isn’t much difference compared to CMake. Those are only reasons; the real point is that the author of luamake also maintains the project’s C++ foundation, so switching isn’t very realistic.
Activity
CppCXY commentedon Feb 2, 2026
The whole project is deeply integrated with luamake — it isn’t just a simple switch of build systems. Moreover, luamake ultimately outputs Ninja files for compilation, so there isn’t much difference compared to CMake. Those are only reasons; the real point is that the author of luamake also maintains the project’s C++ foundation, so switching isn’t very realistic.