neovim

commit d6a6078809b6f750140d84fa0537fbce6e1fa00f
parent 95b03171df223e1fed5de15124a3b9204f37048a
Author: Kevin Goodsell <58675+KevinGoodsell@users.noreply.github.com>
Date:   Mon, 26 Jan 2026 04:41:10 -0800

docs(build): update OpenBSD build notes #37533

Issue: https://github.com/neovim/neovim/issues/37518
Diffstat:
M
BUILD.md
 | 
16
+++++-----------

1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/BUILD.md b/BUILD.md
@@ -477,23 +477,17 @@ If you get an error regarding a `sha256sum` mismatch, where the actual SHA-256 h
 ### OpenBSD
 
 ```sh
-doas pkg_add gmake cmake curl gettext-tools git
+doas pkg_add gmake cmake curl gettext-tools git ninja
 ```
 
-Build can sometimes fail when using the top level `Makefile`, apparently due to some third-party component (see [#2445-comment](https://github.com/neovim/neovim/issues/2445#issuecomment-108124236)). The following instructions use CMake:
+While `ninja` is technically optional, the build is likely to fail without it. This is because `cmake` will use `make` in that case, and the bundled LuaJIT requires `gmake`. Instead of installing `ninja`, you could work around this by installing `luajit` and disabling the bundled LuaJIT:
 
 ```sh
-mkdir .deps
-cd .deps
-cmake ../cmake.deps/
-gmake
-cd ..
-mkdir build
-cd build
-cmake ..
-gmake
+gmake DEPS_CMAKE_FLAGS="-DUSE_BUNDLED_LUAJIT=0"
 ```
 
+Another workaround is to edit `cmake/Deps.cmake` and comment out the line `set(MAKE_PRG "$(MAKE)")`. This will leave `MAKE_PRG` set to `gmake`, so LuaJIT will be built with `gmake`.
+
 ### macOS
 
 #### macOS / Homebrew