| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Dirs "config", "packaging", and "third-party" are all closely related
but this is not obvious from the layout. This adds friction for new
contributors.
Solution:
- rename config/ to cmake.config/
- rename test/config/ to test/cmakeconfig/ because it is used in Lua
tests: require('test.cmakeconfig.paths').
- rename packaging/ to cmake.packaging/
- rename third-party/ to cmake.deps/ (parallel with .deps/)
|
| |
|
|
|
|
| |
This is rarely, if ever, used and certainly not tested. It's likely this
isn't functional anymore.
|
|
|
|
|
|
|
|
|
|
| |
This partially reverts commit f8af81445bb48966d54f4a956842d935d009d275.
The mingw parts of cmake was removed to see if it was still used
(ref: https://github.com/neovim/neovim/pull/18580). It turns out it is,
so this will fix that.
Closes: https://github.com/neovim/neovim/issues/18597
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unnecessary CI builds increase the change of spurious failures, which are costly
noise. Of course, we should fix all legitimate bugs, but we also cannot
micro-manage every platform, so there needs to be a clear motivation for the CI
builds that we maintain.
Reasons against maintaining a mingw CI job:
1. The windows mingw build is slow.
2. Failures:
- https://github.com/neovim/neovim/issues/18494
- https://github.com/neovim/neovim/issues/18495
3. The mingw artifact is 10x bigger than the windows MSVC artifact:
https://github.com/neovim/neovim/issues/10560
4. Our releases publish the MSVC (not mingw) artifact for Windows users:
https://github.com/neovim/neovim/releases
5. Non-MSVCRT has limitations documented by libuv: http://docs.libuv.org/en/v1.x/process.html
> On Windows file descriptors greater than 2 are available to the child process only if the child processes uses the MSVCRT runtime.
Closes https://github.com/neovim/neovim/issues/18551
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Besides bugfixes, this brings `XDG_*` compliance and improved
robustness, especially for network errors.
See https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md
- fixup: set LIBUV_LIBDIR to workaround https://github.com/luarocks/luarocks/commit/83126ba324846b754ffc5e0345341f01262b3f86
- https://github.com/luarocks/luarocks/issues/1214
- https://github.com/luarocks/luarocks/pull/1355
|
|
|
|
|
| |
This bumps the bundled LibLUV to 1.34.1 in order to make the newly introduced `uv.fs_mkstemp` available in the official builds. (The minimum required version remains at 1.30.1.)
The bump of lua-compat-53 to 0.9 is needed to build with the updated LibLUV.
|
| |
|
|
|
| |
Changelog: https://github.com/luarocks/luarocks/compare/v2.4.4..v3.2.1#diff-4ac32a78649ca5bdd8e0ba38b7006a1e
|
| |
|
| |
|
|
|
|
|
|
|
| |
The inspect modules is vendored as `vim.inspect`, and therefore it makes
sense to use this in tests also.
Ref: https://github.com/neovim/neovim/issues/6580
Ref: https://github.com/neovim/neovim/commit/bb3aa824b
|
|
|
|
|
|
|
| |
I found it often irritation to see the same comment about "DEPENDS"
there all the time. This uses the LuaRocks rock name as a comment
instead (which is hard to parse from the recipe), moves the note about
DEPENDS to the top (extended), and fixes/aligns some whitespace.
|
|
|
|
|
|
|
|
| |
With LuaRocks 3 it will include the version, and this will make the
upgrade easier then.
It also makes sense to factor this out in general for clarity already.
Pulled out of https://github.com/neovim/neovim/pull/10292.
|
|
|
|
|
|
|
|
|
|
| |
* build: update some test dependencies
* luacheck ignores
* BuildLua: add ${BUSTED} to depends for ${BUSTED_LUA}
This is required to rebuild it when busted gets updated.
|
|
|
|
|
|
| |
This is meant to make it possible to use `find_package(LuaJit)` etc with
the third-party CMake project in general.
Followup to https://github.com/neovim/neovim/pull/10297/files#r296439576.
|
|
|
| |
This is not necessary and avoids confusion.
|
|
|
|
|
|
|
|
|
| |
This regressed in 204ec6337.
Currently it would detect/use lua5.3 from the system, but in general
luajit is / should be preferred.
Noticed this due to nvim-client failing to build with Lua 5.3
(https://github.com/neovim/lua-client/pull/43).
|
|
|
|
| |
Followup to https://github.com/neovim/neovim/pull/10291
Ref: https://github.com/neovim/neovim/issues/10289
|
|
|
| |
Fixes https://github.com/neovim/neovim/issues/10289
|
|
|
|
|
|
| |
Co-authored-by: Andrey Popp <8mayday@gmail.com>
closes #9546
closes #10084
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The --ignore-whitespace argument was added when applying patches to
prevent failures when patched files have different line endings.
|
|
|
|
|
|
|
| |
Is there a race between the luarocks `make bootstrap` dependencies?
reverts f73b4911312b35bfe38ed068672a2f8ba8875ba7
ref https://github.com/luarocks/luarocks/pull/774
|
|
|
|
| |
upstream: https://github.com/luarocks/luarocks/pull/774
|
| |
|
|
|
|
| |
LuaRocks bundles an outdated wget.exe for downloading packages on Windows. It is too old to support GitHub's TLS, so this patch will replace it with curl.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Tracking master subjects us to breakages (as happened when
luacheck-scm-1.rockspec got renamed to luacheck-dev-1.rockspec) and
makes older releases unbuildable when that happens.
|
| |
|
| |
|
|
|
| |
luacheck renamed the filename from luacheck-scm-1.rockspec to luacheck-dev-1.rockspec.
|
| |
|
|
|
|
| |
ref 6647f3c047b1
closes #7535
|
|
|
|
|
|
| |
LuaRocks 2.3 and onwards changed the /P option to no longer include the
version number which made newer releases of LuaRocks fail when compiling
on Windows.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 54293b73d4bef32eca7f5d6b3a3f177379940a49.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/mpeterv/luacheck/pull/81#issuecomment-261099606
> If you really want to use bleeding-edge version you should get the
> rockspec from master branch, not a fixed commit ...
> The correct way to install from a specific commit is cloning that
> commit and running "luarocks make" from project directory. The reason
> is that running "install" or "build" on an scm rockspec fetches
> sources from master but uses build description from the rockspec
> itself, which may be outdated.
|
|
|
|
|
| |
The argument quotes in the luv build recipe did not work
in Windows.
|
|
|
|
|
| |
Busted now builds on Windows, remove the check. In Windows the binary
is called busted.bat.
|
|
|
|
|
|
| |
penlight 1.4.0 changed how files are being globbed and busted hasn't
been updated accordingly yet. See Olivine-Labs/busted#528 for more
information.
|
|
|
|
|
| |
luarocks has had trouble in the past with multiple build/install
commands running at the same time.
|
|\
| |
| | |
Enable MSYS/MinGW builds in Appveyor
|