opensourcemirror
/
neovim
mirror of https://github.com/neovim/neovim.git
1
0
Fork 0
Code Issues Releases Wiki Activity
neovim/CMakeLists.txt

682 lines
23 KiB
CMake
Raw Normal View History

doc: job/channel, misc #7783 doc: termios defaults. ref #6992 doc: :help shell-powershell doc: provider: Python minimum version is 2.7, 3.4 doc: remove :!start special-case. #5844 doc: mention #7917 change which accepts empty Array for Dictionary parameter doc: <Cmd> pseudokey doc: lmap change #5658 doc: -s, -es
2017-12-27 19:30:23 +01:00
# CMAKE REFERENCE
# intro: https://codingnest.com/basic-cmake/
# best practices (3.0+): https://gist.github.com/mbinna/c61dbb39bca0e4fb7d1f73b0d66a4fd1
ci: Travis: use minimum supported CMake in one job (#10445)
2019-07-08 12:53:43 +02:00
# Version should match the tested CMAKE_URL in .travis.yml.
Raise minimum CMake version to 2.8.12 and remove compat code 2.8.12 is supported by our main CI targets and [repology] confirms that this is broadly supported. [repology]: https://repology.org/metapackage/cmake/information
2018-06-16 16:20:25 +02:00
cmake_minimum_required(VERSION 2.8.12)
cmake: Explicitly declare C as the project language There's a mix of CXX and C related variables being set/referenced in our CMake files. Since we only use C, use an explicit language list of "C" instead of the implicit "C CXX" and replace all uses of CXX variables with their C counterparts
2018-06-15 14:33:07 +02:00
project(nvim C)
Import vim from changeset v5628:c9cad40b4181 - Cleanup source tree, leaving only files necessary for compilation/testing - Process files through unifdef to remove tons of FEAT_* macros - Process files through uncrustify to normalize source code formatting. - Port the build system to cmake
2014-01-31 14:39:15 +01:00
build: get rid of warnings with `cmake --debug-output` (#11131)
2019-10-02 03:44:57 +02:00
if(POLICY CMP0065)
cmake_policy(SET CMP0065 NEW)
endif()
if(POLICY CMP0060)
cmake_policy(SET CMP0060 NEW)
endif()
add custom CMake module path
2014-02-24 21:54:45 +01:00
# Point CMake at any custom modules we may ship
build: fix CMAKE_MODULE_PATH usage Fixes #1447. `CMAKE_MODULE_PATH` is meant to be a list of directories, and as such, is not the proper way to launch our scripts. Let's use `${PROJECT_SOURCE_DIR}/cmake` instead. Also, let's not outright set `CMAKE_MODULE_PATH`, but instead append our location to the list.
2014-11-11 01:26:01 +01:00
list(APPEND CMAKE_MODULE_PATH "${PROJECT_SOURCE_DIR}/cmake")
add custom CMake module path
2014-02-24 21:54:45 +01:00
build: prevent in-tree builds for the time being, as it's not supported
2016-10-12 00:35:02 +02:00
# We don't support building in-tree.
include(PreventInTreeBuilds)
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_property(GLOBAL PROPERTY USE_FOLDERS ON)
Revamp the build system. This achieves several goals: * Less reliance on scripts so we have better portability to Windows (though we still have a ways to go for proper Windows support). Luajit, luarocks, moonscript, and busted are all installed via CMake now. * Trying to make use of pkg-config to get the correct libraries. The latest libuv is still broken in this regard, but we'll at least be in a position to use it. * Allow the use of Ninja or make. The former runs faster in many environments, and automatically makes use of parallel builds. This also allows for system installed dependencies--though not through the Makefile just yet--and adds support for FreeBSD. This also make us build libuv and luajit as static libraries only, since we're only concerned about having static libraries for our bundled dependencies.
2014-03-03 16:09:06 +01:00
# Prefer our bundled versions of dependencies.
build: respect $DEPS_BUILD_DIR Without this, the CI_TARGET=lint travis job cant't find the cached deps (in $HOME/nvim-deps), nor can it update the cache.
2018-03-11 13:15:42 +01:00
if(DEFINED ENV{DEPS_BUILD_DIR})
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
set(DEPS_PREFIX "$ENV{DEPS_BUILD_DIR}/usr" CACHE PATH "Path prefix for finding dependencies")
build: respect $DEPS_BUILD_DIR Without this, the CI_TARGET=lint travis job cant't find the cached deps (in $HOME/nvim-deps), nor can it update the cache.
2018-03-11 13:15:42 +01:00
else()
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
set(DEPS_PREFIX "${CMAKE_CURRENT_SOURCE_DIR}/.deps/usr" CACHE PATH "Path prefix for finding dependencies")
deps: Build bundled dependencies automatically for IDEs Environment variables are used to detect when the project is being built from within Clion or Visual Studio, so that the build process can be simplified by automatically building the bundled dependencies for them.
2018-06-10 16:57:12 +02:00
# When running from within CLion or Visual Studio,
# build bundled dependencies automatically.
if(NOT EXISTS ${DEPS_PREFIX}
AND (DEFINED ENV{CLION_IDE}
OR DEFINED ENV{VisualStudioEdition}))
message(STATUS "Building dependencies...")
set(DEPS_BUILD_DIR ${PROJECT_BINARY_DIR}/.deps)
file(MAKE_DIRECTORY ${DEPS_BUILD_DIR})
execute_process(
COMMAND ${CMAKE_COMMAND} -G ${CMAKE_GENERATOR}
-DCMAKE_TOOLCHAIN_FILE=${CMAKE_TOOLCHAIN_FILE}
-DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
-DCMAKE_C_COMPILER=${CMAKE_C_COMPILER}
-DCMAKE_C_FLAGS=${CMAKE_C_FLAGS}
-DCMAKE_C_FLAGS_DEBUG=${CMAKE_C_FLAGS_DEBUG}
-DCMAKE_C_FLAGS_MINSIZEREL=${CMAKE_C_FLAGS_MINSIZEREL}
-DCMAKE_C_FLAGS_RELWITHDEBINFO=${CMAKE_C_FLAGS_RELWITHDEBINFO}
-DCMAKE_C_FLAGS_RELEASE=${CMAKE_C_FLAGS_RELEASE}
-DCMAKE_MAKE_PROGRAM=${CMAKE_MAKE_PROGRAM}
${PROJECT_SOURCE_DIR}/third-party
WORKING_DIRECTORY ${DEPS_BUILD_DIR})
execute_process(
COMMAND ${CMAKE_COMMAND} --build ${DEPS_BUILD_DIR}
--config ${CMAKE_BUILD_TYPE})
set(DEPS_PREFIX ${DEPS_BUILD_DIR}/usr)
endif()
build: respect $DEPS_BUILD_DIR Without this, the CI_TARGET=lint travis job cant't find the cached deps (in $HOME/nvim-deps), nor can it update the cache.
2018-03-11 13:15:42 +01:00
endif()
deps: Build bundled dependencies automatically for IDEs Environment variables are used to detect when the project is being built from within Clion or Visual Studio, so that the build process can be simplified by automatically building the bundled dependencies for them.
2018-06-10 16:57:12 +02:00
Fix CMakeLists.txt search paths for cross compile
2015-04-19 01:20:26 +02:00
if(CMAKE_CROSSCOMPILING AND NOT UNIX)
list(INSERT CMAKE_FIND_ROOT_PATH 0 ${DEPS_PREFIX})
list(INSERT CMAKE_PREFIX_PATH 0 ${DEPS_PREFIX}/../host/bin)
else()
list(INSERT CMAKE_PREFIX_PATH 0 ${DEPS_PREFIX})
set(ENV{PKG_CONFIG_PATH} "$ENV{PKG_CONFIG_PATH}:${DEPS_PREFIX}/lib/pkgconfig")
endif()
Revamp the build system. This achieves several goals: * Less reliance on scripts so we have better portability to Windows (though we still have a ways to go for proper Windows support). Luajit, luarocks, moonscript, and busted are all installed via CMake now. * Trying to make use of pkg-config to get the correct libraries. The latest libuv is still broken in this regard, but we'll at least be in a position to use it. * Allow the use of Ninja or make. The former runs faster in many environments, and automatically makes use of parallel builds. This also allows for system installed dependencies--though not through the Makefile just yet--and adds support for FreeBSD. This also make us build libuv and luajit as static libraries only, since we're only concerned about having static libraries for our bundled dependencies.
2014-03-03 16:09:06 +01:00
cmake: Enable -fdiagnostics-color=auto gcc flag. #3137
2015-08-27 09:56:46 +02:00
# used for check_c_compiler_flag
include(CheckCCompilerFlag)
build: give priority to /sw and /opt/local on Mac OS X Unfortunately, we can't force the specific inclusion of a header file. So if anything add /opt/local/include to the include path--such as libintl--then other dependencies might be drawn from /opt/local at compile time, even though we detected them elsewhere at configure time. This, in turn, causes issues with mixed versions, such as the iconv.h header being pulled from /opt/local/include, but linked against the library in /usr/lib--which can be mismatched versions. So, despite CMake's best effort to treat /sw and /opt/local as just another system area, we really need to give them preferential treatment. To do this, we add them to CMAKE_PREFIX_PATH. This fixes an issue discovered while re-enabling iconv in #1370.
2014-11-08 22:16:39 +01:00
if(CMAKE_SYSTEM_NAME STREQUAL "Darwin")
# CMake tries to treat /sw and /opt/local as extension of the system path, but
# that doesn't really work out very well. Once you have a dependency that
# resides there and have to add it as an include directory, then any other
# dependency that could be satisfied from there must be--otherwise you can end
# up with conflicting versions. So, let's make them more of a priority having
# them be included as one of the first places to look for dependencies.
list(APPEND CMAKE_PREFIX_PATH /sw /opt/local)
# Work around some old, broken detection by CMake for knowing when to use the
# isystem flag. Apple's compilers have supported this for quite some time
# now.
if(CMAKE_COMPILER_IS_GNUCC)
set(CMAKE_INCLUDE_SYSTEM_FLAG_C "-isystem ")
endif()
win: Define USE_FNAME_CASE (#5962)
2017-01-17 16:32:41 +01:00
endif()
CMakeLists: enable USE_FNAME_CASE on Mac
2015-03-27 04:30:45 +01:00
win: Define USE_FNAME_CASE (#5962)
2017-01-17 16:32:41 +01:00
if(WIN32 OR CMAKE_SYSTEM_NAME STREQUAL "Darwin")
# Enable fixing case-insensitive filenames for Windows and Mac.
CMakeLists: enable USE_FNAME_CASE on Mac
2015-03-27 04:30:45 +01:00
set(USE_FNAME_CASE TRUE)
build: give priority to /sw and /opt/local on Mac OS X Unfortunately, we can't force the specific inclusion of a header file. So if anything add /opt/local/include to the include path--such as libintl--then other dependencies might be drawn from /opt/local at compile time, even though we detected them elsewhere at configure time. This, in turn, causes issues with mixed versions, such as the iconv.h header being pulled from /opt/local/include, but linked against the library in /usr/lib--which can be mismatched versions. So, despite CMake's best effort to treat /sw and /opt/local as just another system area, we really need to give them preferential treatment. To do this, we add them to CMAKE_PREFIX_PATH. This fixes an issue discovered while re-enabling iconv in #1370.
2014-11-08 22:16:39 +01:00
endif()
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
option(ENABLE_LIBINTL "enable libintl" ON)
build/msvc: Add libiconv to bundled dependencies
2018-06-07 03:39:17 +02:00
option(ENABLE_LIBICONV "enable libiconv" ON)
build: Enable LTO (Link Time Optimization) #8654
2018-07-23 03:22:14 +02:00
if (MINGW)
# Disable LTO by default as it may not compile
# See https://github.com/Alexpux/MINGW-packages/issues/3516
# and https://github.com/neovim/neovim/pull/8654#issuecomment-402316672
option(ENABLE_LTO "enable link time optimization" OFF)
else()
option(ENABLE_LTO "enable link time optimization" ON)
endif()
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
message(STATUS "CMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX}")
# Build type.
version: Add compilation info.
2014-11-09 13:52:15 +01:00
if(NOT CMAKE_BUILD_TYPE)
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
message(STATUS "CMAKE_BUILD_TYPE not specified, default is 'Debug'")
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
set(CMAKE_BUILD_TYPE "Debug" CACHE STRING "Choose the type of build" FORCE)
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
else()
message(STATUS "CMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}")
endif()
if(CMAKE_BUILD_TYPE MATCHES Debug)
set(DEBUG 1)
else()
set(DEBUG 0)
version: Add compilation info.
2014-11-09 13:52:15 +01:00
endif()
CMake: Defer setting CACHE CMAKE_BUILD_TYPE. The Visual Studio CMake generator fails to configure if CACHE CMAKE_BUILD_TYPE is set before CMAKE_BUILD_TYPE.
2015-12-20 04:58:47 +01:00
# Set available build types for CMake GUIs.
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
# Other build types can still be set by -DCMAKE_BUILD_TYPE=...
CMake: Defer setting CACHE CMAKE_BUILD_TYPE. The Visual Studio CMake generator fails to configure if CACHE CMAKE_BUILD_TYPE is set before CMAKE_BUILD_TYPE.
2015-12-20 04:58:47 +01:00
set_property(CACHE CMAKE_BUILD_TYPE PROPERTY
cmake: Remove custom "Dev" build-type. (#6932) The main purpose of this build-type was to avoid unwanted ~/.nvimlog files (which could get really big, and also affects performance) for non-devs. But that is no longer necessary since the log system now avoids non-critical logging by default (#6827). This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
2017-06-29 09:29:40 +02:00
STRINGS "Debug" "Release" "MinSizeRel" "RelWithDebInfo")
CMake: Defer setting CACHE CMAKE_BUILD_TYPE. The Visual Studio CMake generator fails to configure if CACHE CMAKE_BUILD_TYPE is set before CMAKE_BUILD_TYPE.
2015-12-20 04:58:47 +01:00
version: semver.org compliance We use `git describe` to stamp pre-release versions (dev builds). But `git describe` uses the result of the most-recent tag (the current _release_ version)--so we must munge it with the _next_ (i.e. unreleased) version. Also fix non-git builds: do not invoke git_describe(NVIM_VERSION_MEDIUM) if we're not in a git tree, else it gets the dummy value "HEAD-HASH-NOTFOUND". Example :version output in non-git build: NVIM 0.1.2-dev Example :version output in git build: NVIM v0.1.2-176-g9c3c2b5
2015-12-13 18:29:02 +01:00
# If not in a git repo (e.g., a tarball) these tokens define the complete
api: api_info()['version'] API level is disconnected from NVIM version. The API metadata holds the current API level, and the lowest backwards-compatible level supported by this instance. Release 0.1.6 is the first release that reports the Nvim version and API level. metadata['version'] = { major: 0, minor: 1, patch: 6, api_level: 1, api_compatible: 0, api_prerelease: false, } The API level may remain unchanged across Nvim releases if the API has not changed. When changing the API, - set NVIM_API_PRERELEASE to true - increment NVIM_API_LEVEL (at most once per Nvim version) - adjust NVIM_API_LEVEL_COMPAT if backwards-compatibility was broken api_level_0.mpack was generated from Nvim 0.1.5 with: nvim --api-info
2016-10-26 15:20:00 +02:00
# version string, else they are combined with the result of `git describe`.
version: report commit hash as "build number" in long version string
2014-10-05 00:32:47 +02:00
set(NVIM_VERSION_MAJOR 0)
version bump
2019-09-16 01:19:49 +02:00
set(NVIM_VERSION_MINOR 5)
version bump
2018-12-31 00:44:49 +01:00
set(NVIM_VERSION_PATCH 0)
version bump
2019-09-16 01:19:49 +02:00
set(NVIM_VERSION_PRERELEASE "-dev") # for package maintainers
version: Prepare for releases. * Hide commit information from --version if we can't find any (e.g. when building from tarball). To define a release in CMake, set NVIM_VERSION_PRERELEASE to "". This will modify --version output to: * Show annotated Git tag instead of commit hash (NVIM_VERSION_COMMIT). * Hide commit date (NVIM_VERSION_BUILD).
2015-09-28 12:17:19 +02:00
api: api_info()['version'] API level is disconnected from NVIM version. The API metadata holds the current API level, and the lowest backwards-compatible level supported by this instance. Release 0.1.6 is the first release that reports the Nvim version and API level. metadata['version'] = { major: 0, minor: 1, patch: 6, api_level: 1, api_compatible: 0, api_prerelease: false, } The API level may remain unchanged across Nvim releases if the API has not changed. When changing the API, - set NVIM_API_PRERELEASE to true - increment NVIM_API_LEVEL (at most once per Nvim version) - adjust NVIM_API_LEVEL_COMPAT if backwards-compatibility was broken api_level_0.mpack was generated from Nvim 0.1.5 with: nvim --api-info
2016-10-26 15:20:00 +02:00
# API level
multigrid: API version bump
2018-12-31 12:54:57 +01:00
set(NVIM_API_LEVEL 6) # Bump this after any API change.
api: api_info()['version'] API level is disconnected from NVIM version. The API metadata holds the current API level, and the lowest backwards-compatible level supported by this instance. Release 0.1.6 is the first release that reports the Nvim version and API level. metadata['version'] = { major: 0, minor: 1, patch: 6, api_level: 1, api_compatible: 0, api_prerelease: false, } The API level may remain unchanged across Nvim releases if the API has not changed. When changing the API, - set NVIM_API_PRERELEASE to true - increment NVIM_API_LEVEL (at most once per Nvim version) - adjust NVIM_API_LEVEL_COMPAT if backwards-compatibility was broken api_level_0.mpack was generated from Nvim 0.1.5 with: nvim --api-info
2016-10-26 15:20:00 +02:00
set(NVIM_API_LEVEL_COMPAT 0) # Adjust this after a _breaking_ API change.
NVIM v0.4.0 This release represents ~2700 commits since v0.3.4, the previous non-maintenance release. Besides the highlights listed below, this release features vast improvements to documentation, internal subsystems and test/CI infrastructure, and 700+ patches merged from Vim. FEATURES: New API functions: nvim_create_buf: create various kinds of buffers nvim_get_context, nvim_load_context 8e6b0a73c91b #10619 API: Context: save/restore/inspect editor state nvim_input_mouse: perform mouse actions nvim_open_win: create floating windows (and external, for supporting UIs) nvim_paste: paste text at cursor nvim_put: put text at cursor nvim_select_popupmenu_item: perform popupmenu actions nvim_set_keymap: create/delete mappings nvim_set_vvar: set v: variables nvim_ui_pum_set_height nvim_ui_try_resize_grid nvim_win_close: close windows nvim_win_get_config: get window configuration nvim_win_set_config: reconfigure windows New UI events: redraw.grid_destroy redraw.hl_group_set 8a3f8589a3ed #10504 UI/highlight: expose builtin highlight groups using hl_group_set event redraw.msg_clear redraw.msg_history_show redraw.msg_ruler redraw.msg_set_pos redraw.msg_show redraw.msg_showcmd redraw.msg_showmode redraw.win_close redraw.win_external_pos redraw.win_float_pos redraw.win_hide redraw.win_pos API f5c56f03bb9e #9170 API/Lua: nvim_buf_attach: support Lua callback 82d48c0dab0f #9896 API: emit nvim_error_event on failed async request b9ad12e6c2fa #9992 UI/nvim_ui_attach(): add `override` option 3d1ed7c95901 #9993 UI/ext_messages: learn more message kinds 8ed54bbec3b0 #9547 proper multiline error message for rpcrequest, API wrappers Lua This release introduces "Nvim-Lua standard library". See ":help lua-stdlib". 89d7e24891c2 #9463 Lua stdlib: vim.inspect, string functions 8e941c59ec23 #9740 Lua: generate documentation from docstrings 1cbe0145695b #9301 lua/stdlib: Introduce vim.shared c83926cd0aa5 #10123 Lua: introduce vim.loop (expose libuv event-loop) 81e1dbca99c1 #10120 Lua: vim.schedule(cb) 1f54f68732b4 #10688 Lua: minimal UTF-16 support needed for LSP 6fb0020df4eb #10513 Lua encoding support c0993ed3433e Lua: support getting UTF-32 and UTF-16 sizes of replaced text b0e26199ec02 Lua: add {old_byte_size} to on_lines buffer change event UI: - The Nvim 0.3.4 UI protocol introduced line-based updates instead of legacy char-based updates. Nvim 0.4 continues to evolve the UI protocol. See ":help ui". Legacy UI clients are supported. See ":help api-contract". 9a1675b06539 #6619 Floating windows - Can be (re)positioned, anchored, external. - Are real windows showing real buffers. No shortcuts, hacks, or compromises. - Support all features and API of normal windows, plus more. 6427894d8911 #8455 Multigrid: "windows drawn on separate grids" - Windows are logically isolated internally. - Windows are sent to UIs as distinct objects, so that UIs can control layout instead of being stuck with the classic TUI layout. - Per-window font-size, dimenions, line-spacing. - Compositor: Internal subsystem for composing grids. 3855204f5860 #6917 UIEnter, UILeave 788bcbba2465 #9923 ui: ":syn blend=", 'winblend' 7cf7c0a0b8e9 #9575 ui: 'redrawdebug' option for flexible debugging of redrawing 5c836d2ef8b6 #9607 wildoptions=pum (enabled by default) 37f8df882463 #9571 UI: 'pumblend' option for semi-transparent popupmenu c403a95a5297 #9446 Visual: highlight char-at-cursor - Traditionally Vim's visual selection does "reverse mode", which perhaps conflicts with the non-blinking block cursor. But 'guicursor' defaults to a vertical bar for selection=exclusive, and this confuses users who expect to see the text highlighted. :terminal fc27dc98d74f #8550 autocmds: TermEnter, TermLeave d13803f64fc5 #9810 keymap, terminal: more keycodes 3b56f59532ac #9535 :terminal : Fix F1-F4 key codes 2d4a37ebab35 #10370 :ls : show "R", "F" for terminal-jobs fd0fd752c872 #9966 terminal: swap priority of terminal, editor highlights 7bb858c39cac #9494 libvterm 0.1 TUI 3afb397407af syntax, TUI: support "strikethrough" ccbcd390d42d #9408 TUI: "title stacking" unconditionally 298608f88c46 #9509 TUI: detect background color, set bg=dark/light 42f492ac9905 #9097 TUI: handle Smulx extension capability (extended underline) 424ddd01f588 #10205 TUI: support rgba background detection 9b4383261a3d #9601 TUI: italics in tmux, Terminal.app f6fb370b1bcc #9793 keymap: support more (keypad) keycodes 3340e08becbf #9423 TUI: Konsole DECSCUSR fixup :checkhealth d0fd66ba82c4 health/provider.vim: check curl HTTPS support c38862aceabe #10490 checkhealth: try yarn if npm is missing 43356a43d00f #9929 health: check if tmux enabled true colors ec5a4d862d71 #9548 checkhealth: validate locale providers (clipboard, python, etc.): 96be8a2c4d63 #10161 Allow reloading providers (useful for UIs/clients) db3c797c6b3c #9487 provider: improve error message if provider is missing Various: 36762a00a801 #9295 signs: support multiple columns 801fe799ff35 #10382 eval: wait() (wait for any condition) 9df3a676e7f2 #10400 MsgArea highlight; message grid a9bea8c1047f #10790 keymap: allow modifiers to multibyte chars, like <m-ä> 25e0a449bb66 #10878 #4448 paste: redesign (10x+ faster pasting; extensible vim.paste Lua hook) ef5037e7f6e1 #9706 autocmd: introduce "++once" feature 175398f21645 #9616 add CompleteChanged autocmd 7fcf2f926fc6 #9717 TextYankPost: add v:event["inclusive"] 3a699a790c14 #8364 termdebug.vim plugin ca1ce590257c #9709 performance: use os_copy to create backups ed0e96cd28f8 man.vim: set 'linebreak' 70f6939fd4b5 #9564 events: add "Signal" event f89d0d8230f3 #9568 inccommand: auto-disable if folding is slow FIXES: 41bb68b8e8d0 #10584 process_stop: uv: do not close stdin first/explicitly e50aa2a6c654 #10117 normal: Don't exit CTRL-O mode after processing K_EVENT 95fa71c6d2b4 #9504 :recover : Fix crash on non-existent *.swp 5a836d4767b7 #9507 screen: don't unconditionally clear messages on window scroll 149dcbf2c762 #10021 channel: refactor events, prevent recursive invocation of events d19ff73b39a9 #10107 Fix multiple c_CTRL-D showing statusline b65a7b7f6692 #10103 Fix wildmode=list,full and display+=msgsep interaction 0be6d3c86fe5 #9634 fsync: Ignore ENOTSUP. Fix writing to SMB. b247c6fd2255 #10025 kbtree: pointer UB and unitialized value fixes 018e0d5a19c3 #9643 API/buffer-updates: always detach on buf-reload 400ee59247ea #9961 API: fix cursor position when lines are added 769f44e918c6 #9911 win/defaults: Use "…/nvim-data/site" in 'runtimepath' 83d571653bdc #9911 spellfile.vim: store files in stdpath('data') 8dbf23181add #9887 RPC: conform message-id type to msgpack-RPC spec 5f996e36d102 #9894 options: properly reset directories on 'autochdir' 4c4a57015687 #9807 various CursorMoved fixes 943bedfc86ab #9853 event-loop: do not set CA_COMMAND_BUSY 9d207fd87617 #9693 dictwatcheradd(): support b:changedtick 2d50bf349883 #9789 mac: fix locale detection c5631338b16b #9754 :mksession : restore tab-local working directories 092e7e6c6058 #9703 #9703 executable(): return false if user is not owner 11a481f711ee #9686 env var fixes/improvements 8e54847fdf3c #9666 #7920 os/env: Fix completion of multibyte env var names 519382646be3 #10468 Fix is_executable_in_path() on Windows 8eaa452073a1 #9516 win: exepath(), executable() fixes f55c1e4233a4 #10544 reltimefloat(): allow negative result b08dc3ec195f #10561 win: jobstart(), system(): $PATHEXT-resolve exe 7cc2b723d43c #10392 TextYankPost: spurious/too-early dispatch during delete 6e01ed6a4c85 OpenBSD: stop jobs/processes properly 58dd5fcc01ed #10522 jobstop(): close channel before process_stop() 83632022f84e #10959 improved resize behavior (all UIs) c6eb1f42bec0 #10830 API: fix nvim_command_output buffer overflow cbfd18c85acd #10763 startup: handle 'guicursor' after user config b8f2436febcc #10915 jobwait(): fix race if job exits quickly 2fafed6bb8aa #10765 clipboard: handle/avoid SIGTERM with previous owner 8aca932aa0ac #9954 clipboard: setreg("*") with clipboard=unnamed 3f10c5b5338f #9480 performance: clipboard/macOS: assume that pbcopy works 48efafc81c84 #10398 screen: disable redrawing inside VimResized 5e4b93a38f1e #10389 API/Lua: make nvim_execute_lua use native lua floats, not special tables 8c6f5b7f9268 #9934 Spurious quote mark in command line when typing <C-R> a8a38f346548 Lua 5.2/5.3 compat :terminal 47b7b471fa0f #10700 :terminal : update buffer when switching tabpage 5225c1ec302f #9605 terminal: Fix potential invalid local 'scrollback' 894f6bee54e8 #8325 :terminal : set topline based on window height 8171e96b9640 #9551 Improve :terminal resize d928b036dc2b #9856 :stopinsert should leave terminal-mode 3f712185058f #9926 :terminal : fix: Using `:stopinsert` while in normal mode 5020daa6e5ce #9883 ui/terminal: make terminal state redraw like any other state TUI: 9f19e8d29dce #9443 TUI: Do not disable BCE for builtin terminfos a4076e5dcf66 #9474 win/TUI: fix text overrides line numbers 533d4a36ec03 #9645 TUI: do not resize host-terminal on startup b51e5d8b8dd2 #9688 tui_tk_ti_getstr: handle weird value 1f5eac1115a4 #10785 TUI: fix data-race during resize CHANGES: 9697c7f56a26 #8194 fix menu_get() 7f2e43c637e5 #9520 improve Lua error messages c2343180d74f #9526 Remove jemalloc baf93d96063c #9581 UI: always use concrete colors for default_colors_set 91688b488310 #9563 defaults: set 'scrollback' to -1 by default bb24fec33355 #10136 defaults: exclude "S" from 'shortmess' ddd0eb6f5120 #8540 startup: -es/-Es (silent/batch mode): skip swapfile 35362495c965 #9805 jumplist: avoid extra tail entry 939d9053bdf2 #10573 channels: reflect exit due to signals in exit status code 45c34bd84aa5 #10689 :doautocmd : Never show "No matching autocommands" fb19aeeb33f7 #9110 API: make nvim_win_set_option() set window-global, not buffer-local abfc8b3257f8 #10778 emsg_multiline: log Vim errors 06d9cc734bf0 #10657 exists("$FOO"): return false for empty env var 6616d1d3e5c9 #10743 win/env: Vim-compat: Empty string deletes env var 7d664837e1a9 #10662 win: expand nested env var in $HOME 2816bc8620ca #8349 edit.c: Disable indent during completion 58f505dc7432 #9829 startup: remove TUI init special-case Historically Vim/Nvim does backflips to handle input and show messages before a UI is available. This logical contradiction was already fixed for remote UIs (#9024 c236e80cf3df). Fixing it also for the TUI avoids problems on Windows, simplifies the logic, and avoids races like #9959.
2019-09-15 21:38:40 +02:00
set(NVIM_API_PRERELEASE false)
api: Nvim version, API level #5386 The API level is disconnected from the NVIM version. The API metadata holds the current API level, and the lowest backwards-compatible level supported by this instance. Release 0.1.6 will be the first release reporting the Nvim version and API level. metadata['version'] = { major: 0, minor: 1, patch: 6, prerelease: true, api_level: 1, api_compatible: 0, } The API level may remain unchanged across Neovim releases if the API has not changed. When changing the API the CMake variable NVIM_API_PRERELEASE is set to true, and NVIM_API_CURRENT/NVIM_API_COMPATIBILITY are incremented accordingly. The functional tests check the API table against fixtures of past versions of Neovim. It compares all the functions in the old table with the new one, it does ignore some metadata attributes that do not alter the function signature or were removed since 0.1.5. Currently the only fixture is 0.mpack, generated from Neovim 0.1.5 with nvim --api-info.
2016-09-25 19:46:37 +02:00
version: Add compilation info.
2014-11-09 13:52:15 +01:00
set(NVIM_VERSION_BUILD_TYPE "${CMAKE_BUILD_TYPE}")
# NVIM_VERSION_CFLAGS set further below.
Import vim from changeset v5628:c9cad40b4181 - Cleanup source tree, leaving only files necessary for compilation/testing - Process files through unifdef to remove tons of FEAT_* macros - Process files through uncrustify to normalize source code formatting. - Port the build system to cmake
2014-01-31 14:39:15 +01:00
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
log: Always enable; remove DISABLE_LOG - Establish ERROR log level as "critical". Such errors are rare and will be valuable when users encounter unusual circumstances. - Set -DMIN_LOG_LEVEL=3 for release-type builds
2017-05-30 02:03:08 +02:00
# Minimize logging for release-type builds.
if(NOT CMAKE_C_FLAGS_RELEASE MATCHES DMIN_LOG_LEVEL)
set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -DMIN_LOG_LEVEL=3")
CMake: Disable logging for release build types. These are: Release, MinSizeRel, and RelWithDebInfo. Closes #2913.
2015-09-28 12:15:55 +02:00
endif()
log: Always enable; remove DISABLE_LOG - Establish ERROR log level as "critical". Such errors are rare and will be valuable when users encounter unusual circumstances. - Set -DMIN_LOG_LEVEL=3 for release-type builds
2017-05-30 02:03:08 +02:00
if(NOT CMAKE_C_FLAGS_MINSIZEREL MATCHES DMIN_LOG_LEVEL)
set(CMAKE_C_FLAGS_MINSIZEREL "${CMAKE_C_FLAGS_MINSIZEREL} -DMIN_LOG_LEVEL=3")
CMake: Disable logging for release build types. These are: Release, MinSizeRel, and RelWithDebInfo. Closes #2913.
2015-09-28 12:15:55 +02:00
endif()
log: Always enable; remove DISABLE_LOG - Establish ERROR log level as "critical". Such errors are rare and will be valuable when users encounter unusual circumstances. - Set -DMIN_LOG_LEVEL=3 for release-type builds
2017-05-30 02:03:08 +02:00
if(NOT CMAKE_C_FLAGS_RELWITHDEBINFO MATCHES DMIN_LOG_LEVEL)
set(CMAKE_C_FLAGS_RELWITHDEBINFO "${CMAKE_C_FLAGS_RELWITHDEBINFO} -DMIN_LOG_LEVEL=3")
CMake: Disable logging for release build types. These are: Release, MinSizeRel, and RelWithDebInfo. Closes #2913.
2015-09-28 12:15:55 +02:00
endif()
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
# Log level (MIN_LOG_LEVEL in log.h)
if("${MIN_LOG_LEVEL}" MATCHES "^$")
ci/build.ps1: Respect CMAKE_BUILD_TYPE if provided #9869
2019-04-09 00:17:07 +02:00
message(STATUS "MIN_LOG_LEVEL not specified, default is 1 (INFO)")
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
else()
if(NOT MIN_LOG_LEVEL MATCHES "^[0-3]$")
message(FATAL_ERROR "invalid MIN_LOG_LEVEL: " ${MIN_LOG_LEVEL})
endif()
message(STATUS "MIN_LOG_LEVEL=${MIN_LOG_LEVEL}")
endif()
# Default to -O2 on release builds.
if(CMAKE_C_FLAGS_RELEASE MATCHES "-O3")
message(STATUS "Replacing -O3 in CMAKE_C_FLAGS_RELEASE with -O2")
string(REPLACE "-O3" "-O2" CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
endif()
cmake: Remove custom "Dev" build-type. (#6932) The main purpose of this build-type was to avoid unwanted ~/.nvimlog files (which could get really big, and also affects performance) for non-devs. But that is no longer necessary since the log system now avoids non-critical logging by default (#6827). This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
2017-06-29 09:29:40 +02:00
if(CMAKE_COMPILER_IS_GNUCC)
check_c_compiler_flag(-Og HAS_OG_FLAG)
else()
set(HAS_OG_FLAG 0)
CMake: Add custom Dev build type. Introduce new build type Dev that replaces RelWithDebInfo for development builds off master and has optimizations, debug info, and logging enabled. Keep assertions enabled for RelWithDebInfo.
2015-09-28 12:14:38 +02:00
endif()
build: set MIN_LOG_LEVEL correctly (#7419) closes #7283 regression by 42d892913daa215c27e41b2255e96c1ce09ea56c - Don't need to explicitly put "-O2 -g" in RelWithDebInfo; CMake does that already. That was left-over from 42d892913daa2 which removed the "Dev" custom build-type, but repurposed the logic for RelWithDebInfo. - `if(DEFINED MIN_LOG_LEVEL)` doesn't work. - `if(${MIN_LOG_LEVEL} MATCHES "^$")` doesn't work if -DMIN_LOG_LEVEL is omitted. - `if(MIN_LOG_LEVEL)` also isn't what we want: it would be true if MIN_LOG_LEVEL=0.
2017-10-21 02:30:21 +02:00
#
# Build-type: RelWithDebInfo
#
cmake: Remove custom "Dev" build-type. (#6932) The main purpose of this build-type was to avoid unwanted ~/.nvimlog files (which could get really big, and also affects performance) for non-devs. But that is no longer necessary since the log system now avoids non-critical logging by default (#6827). This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
2017-06-29 09:29:40 +02:00
if(HAS_OG_FLAG)
build: set MIN_LOG_LEVEL correctly (#7419) closes #7283 regression by 42d892913daa215c27e41b2255e96c1ce09ea56c - Don't need to explicitly put "-O2 -g" in RelWithDebInfo; CMake does that already. That was left-over from 42d892913daa2 which removed the "Dev" custom build-type, but repurposed the logic for RelWithDebInfo. - `if(DEFINED MIN_LOG_LEVEL)` doesn't work. - `if(${MIN_LOG_LEVEL} MATCHES "^$")` doesn't work if -DMIN_LOG_LEVEL is omitted. - `if(MIN_LOG_LEVEL)` also isn't what we want: it would be true if MIN_LOG_LEVEL=0.
2017-10-21 02:30:21 +02:00
set(CMAKE_C_FLAGS_RELWITHDEBINFO "${CMAKE_C_FLAGS_RELWITHDEBINFO} -Og -g")
endif()
# We _want_ assertions in RelWithDebInfo build-type.
if(CMAKE_C_FLAGS_RELWITHDEBINFO MATCHES DNDEBUG)
cmake: Remove custom "Dev" build-type. (#6932) The main purpose of this build-type was to avoid unwanted ~/.nvimlog files (which could get really big, and also affects performance) for non-devs. But that is no longer necessary since the log system now avoids non-critical logging by default (#6827). This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
2017-06-29 09:29:40 +02:00
string(REPLACE "-DNDEBUG" "" CMAKE_C_FLAGS_RELWITHDEBINFO "${CMAKE_C_FLAGS_RELWITHDEBINFO}")
CMake: Add custom Dev build type. Introduce new build type Dev that replaces RelWithDebInfo for development builds off master and has optimizations, debug info, and logging enabled. Keep assertions enabled for RelWithDebInfo.
2015-09-28 12:14:38 +02:00
endif()
build: `oldtest` target: TEST_FILE, NVIM_PRG (#6098) - Add support for TEST_FILE to the `oldtest` target, for consistency with the busted/lua tests. Caveat: with the busted/lua tests TEST_FILE takes a full path, whereas for `oldtest` it must be "test_foo.res". - Add support for NVIM_PRG, again so that all test-related targets are consistent. - Use consistent name for NVIM_PRG. But still need to support NVIM_PROG for QuickBuild CI. Note: The `oldtest` target is driven by the top-level Makefile, because it requires a TTY. CMake 3.2 added a USES_TERMINAL flag to add_custom_target(). But we support CMake 2.8... add_custom_target(oldtest COMMAND make clean COMMAND make NVIM_PRG=$<TARGET_FILE:nvim> $ENV{MAKEOVERRIDES} DEPENDS nvim WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/testdir" USES_TERMINAL true )
2017-02-12 01:02:54 +01:00
# gcc 4.0+ sets _FORTIFY_SOURCE=2 automatically. This currently
build: turn down the _FORTIFY_SOURCE level on gcc >= 4.0
2014-11-04 23:06:18 +01:00
# does not work with Neovim due to some uses of dynamically-sized structures.
build: `oldtest` target: TEST_FILE, NVIM_PRG (#6098) - Add support for TEST_FILE to the `oldtest` target, for consistency with the busted/lua tests. Caveat: with the busted/lua tests TEST_FILE takes a full path, whereas for `oldtest` it must be "test_foo.res". - Add support for NVIM_PRG, again so that all test-related targets are consistent. - Use consistent name for NVIM_PRG. But still need to support NVIM_PROG for QuickBuild CI. Note: The `oldtest` target is driven by the top-level Makefile, because it requires a TTY. CMake 3.2 added a USES_TERMINAL flag to add_custom_target(). But we support CMake 2.8... add_custom_target(oldtest COMMAND make clean COMMAND make NVIM_PRG=$<TARGET_FILE:nvim> $ENV{MAKEOVERRIDES} DEPENDS nvim WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/testdir" USES_TERMINAL true )
2017-02-12 01:02:54 +01:00
# https://github.com/neovim/neovim/issues/223
build: probe the compiler to see if we need to turn down _FORTIFY_SOURCE Some builds don't use Release (such as Gentoo, though it can be told to). So let's go a bit further and probe the compiler to see if we need to turn down the _FORTIFY_SOURCE level.
2014-11-21 09:42:59 +01:00
include(CheckCSourceCompiles)
build: include the flags for the build type in the _FORTIFY_SOURCE check It turns out the check was being performed without optimizations enabled even when the CMAKE_BUILD_TYPE was set to a release build. This led to _FORTIFY_SOURCE's level not being correctly determined, and us failing to apply the correct workaround. To counter this, we'll take the default flags for the build type and apply them. Also, if options are passed via CFLAGS, they are automatically passed on to the underlying build. So this should cover all the necessary ground. This fixes #1647.
2014-12-16 12:02:42 +01:00
# Include the build type's default flags in the check for _FORTIFY_SOURCE,
# otherwise we may incorrectly identify the level as acceptable and find out
# later that it was not when optimizations were enabled. CFLAGS is applied
# even though you don't see it in CMAKE_REQUIRED_FLAGS.
set(INIT_FLAGS_NAME CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE})
string(TOUPPER ${INIT_FLAGS_NAME} INIT_FLAGS_NAME)
if(${INIT_FLAGS_NAME})
set(CMAKE_REQUIRED_FLAGS "${${INIT_FLAGS_NAME}}")
endif()
CMake: Add #include in _FORTIFY_SOURCE check. #4214 Some toolchains apparently set _FORTIFY_SOURCE=2 in internal header files. Include <string.h> (which in turn should include such internal header files) before checking the value of _FORTIFY_SOURCE to catch that. Fixes #4183.
2016-02-09 22:22:30 +01:00
# Include <string.h> because some toolchains define _FORTIFY_SOURCE=2 in
# internal header files, which should in turn be #included by <string.h>.
build: probe the compiler to see if we need to turn down _FORTIFY_SOURCE Some builds don't use Release (such as Gentoo, though it can be told to). So let's go a bit further and probe the compiler to see if we need to turn down the _FORTIFY_SOURCE level.
2014-11-21 09:42:59 +01:00
check_c_source_compiles("
CMake: Add #include in _FORTIFY_SOURCE check. #4214 Some toolchains apparently set _FORTIFY_SOURCE=2 in internal header files. Include <string.h> (which in turn should include such internal header files) before checking the value of _FORTIFY_SOURCE to catch that. Fixes #4183.
2016-02-09 22:22:30 +01:00
#include <string.h>
build: probe the compiler to see if we need to turn down _FORTIFY_SOURCE Some builds don't use Release (such as Gentoo, though it can be told to). So let's go a bit further and probe the compiler to see if we need to turn down the _FORTIFY_SOURCE level.
2014-11-21 09:42:59 +01:00
#if defined(_FORTIFY_SOURCE) && _FORTIFY_SOURCE > 1
#error \"_FORTIFY_SOURCE > 1\"
#endif
int
main(void)
{
return 0;
}
CMake: Fix _FORTIFY_SOURCE detection when using hardening-wrapper. #2788 When checking code with check_c_source_compiles, the "check variable" (for the _FORTIFY_SOURCE detection: previously _FORTIFY_SOURCE_ACCEPTABLE, now HAS_ACCEPTABLE_FORTIFY) is passed to the compiler like -D_FORTIFY_SOURCE_ACCEPTABLE. This throws off hardening-wrapper [1], which then NOT sets _FORTIFY_SOURCE=2 for the check, assuming it had already been set manually as it detected -D_FORTIFY_SOURCE*. Renaming the "check variable" to not match this pattern works around this problem. [1] https://github.com/thestinger/hardening-wrapper
2015-06-04 11:08:26 +02:00
" HAS_ACCEPTABLE_FORTIFY)
build: probe the compiler to see if we need to turn down _FORTIFY_SOURCE Some builds don't use Release (such as Gentoo, though it can be told to). So let's go a bit further and probe the compiler to see if we need to turn down the _FORTIFY_SOURCE level.
2014-11-21 09:42:59 +01:00
CMake: Fix _FORTIFY_SOURCE detection when using hardening-wrapper. #2788 When checking code with check_c_source_compiles, the "check variable" (for the _FORTIFY_SOURCE detection: previously _FORTIFY_SOURCE_ACCEPTABLE, now HAS_ACCEPTABLE_FORTIFY) is passed to the compiler like -D_FORTIFY_SOURCE_ACCEPTABLE. This throws off hardening-wrapper [1], which then NOT sets _FORTIFY_SOURCE=2 for the check, assuming it had already been set manually as it detected -D_FORTIFY_SOURCE*. Renaming the "check variable" to not match this pattern works around this problem. [1] https://github.com/thestinger/hardening-wrapper
2015-06-04 11:08:26 +02:00
if(NOT HAS_ACCEPTABLE_FORTIFY)
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(STATUS "Unsupported _FORTIFY_SOURCE found, forcing _FORTIFY_SOURCE=1")
Detect and propagate _FORTIFY_SOURCE prefix Get prefix to a -D_FORTIFY_SOURCE string if it is present in CFLAGS and apply the prefix to flags added to redefine _FORTIFY_SOURCE in CFLAGS and CPPFLAGS * fixes 1569
2014-12-12 18:45:21 +01:00
# Extract possible prefix to _FORTIFY_SOURCE (e.g. -Wp,-D_FORTIFY_SOURCE).
STRING(REGEX MATCH "[^\ ]+-D_FORTIFY_SOURCE" _FORTIFY_SOURCE_PREFIX "${CMAKE_C_FLAGS}")
STRING(REPLACE "-D_FORTIFY_SOURCE" "" _FORTIFY_SOURCE_PREFIX "${_FORTIFY_SOURCE_PREFIX}" )
cmake: Build with -fstack-protector-strong if available #2597 If not available, fall back to -fstack-protector + --param=ssp-buffer-size=4 If that isn't available, do nothing. See the following articles for more information: https://lwn.net/Articles/584225/ https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/
2015-08-27 00:00:33 +02:00
if(NOT _FORTIFY_SOURCE_PREFIX STREQUAL "")
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(STATUS "Detected _FORTIFY_SOURCE Prefix=${_FORTIFY_SOURCE_PREFIX}")
Detect and propagate _FORTIFY_SOURCE prefix Get prefix to a -D_FORTIFY_SOURCE string if it is present in CFLAGS and apply the prefix to flags added to redefine _FORTIFY_SOURCE in CFLAGS and CPPFLAGS * fixes 1569
2014-12-12 18:45:21 +01:00
endif()
build: turn down the _FORTIFY_SOURCE level on gcc >= 4.0
2014-11-04 23:06:18 +01:00
# -U in add_definitions doesn't end up in the correct spot, so we add it to
# the flags variable instead.
Detect and propagate _FORTIFY_SOURCE prefix Get prefix to a -D_FORTIFY_SOURCE string if it is present in CFLAGS and apply the prefix to flags added to redefine _FORTIFY_SOURCE in CFLAGS and CPPFLAGS * fixes 1569
2014-12-12 18:45:21 +01:00
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${_FORTIFY_SOURCE_PREFIX}-U_FORTIFY_SOURCE ${_FORTIFY_SOURCE_PREFIX}-D_FORTIFY_SOURCE=1")
build: turn down the _FORTIFY_SOURCE level on gcc >= 4.0
2014-11-04 23:06:18 +01:00
endif()
CMake: Remove --sort-common from linker flags. Workaround for bugs reported at #2641 and #3374. Root cause for this problem is still unknown. Resolves #2641 and resolves #3374.
2015-09-30 20:38:34 +02:00
# Remove --sort-common from linker flags, as this seems to cause bugs (see #2641, #3374).
# TODO: Figure out the root cause.
if(CMAKE_EXE_LINKER_FLAGS MATCHES "--sort-common" OR
CMAKE_SHARED_LINKER_FLAGS MATCHES "--sort-common" OR
CMAKE_MODULE_LINKER_FLAGS MATCHES "--sort-common")
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(STATUS "Removing --sort-common from linker flags")
CMake: Remove --sort-common from linker flags. Workaround for bugs reported at #2641 and #3374. Root cause for this problem is still unknown. Resolves #2641 and resolves #3374.
2015-09-30 20:38:34 +02:00
string(REGEX REPLACE ",--sort-common(=[^,]+)?" "" CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS}")
string(REGEX REPLACE ",--sort-common(=[^,]+)?" "" CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}")
string(REGEX REPLACE ",--sort-common(=[^,]+)?" "" CMAKE_MODULE_LINKER_FLAGS "${CMAKE_MODULE_LINKER_FLAGS}")
# If no linker flags remain for a -Wl argument, remove it.
# '-Wl$' will match LDFLAGS="-Wl,--sort-common",
# '-Wl ' will match LDFLAGS="-Wl,--sort-common -Wl,..."
string(REGEX REPLACE "-Wl($| )" "" CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS}")
string(REGEX REPLACE "-Wl($| )" "" CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}")
string(REGEX REPLACE "-Wl($| )" "" CMAKE_MODULE_LINKER_FLAGS "${CMAKE_MODULE_LINKER_FLAGS}")
endif()
build: linux does not always have execinfo.h (#7101) Closes #7099
2017-07-30 23:02:41 +02:00
check_c_source_compiles("
#include <execinfo.h>
int main(void)
{
void *trace[1];
cmakelists: fixed tests to avoid clang warnings (#10705) * clang/"dead assignment" * clang/"Uninitialized argument value"
2019-08-07 12:49:33 +02:00
backtrace(trace, 1);
build: linux does not always have execinfo.h (#7101) Closes #7099
2017-07-30 23:02:41 +02:00
return 0;
}
" HAVE_EXECINFO_BACKTRACE)
CMake: Feature-detect __builtin_{add,sub}_overflow
2019-01-08 22:00:52 +01:00
check_c_source_compiles("
int main(void)
{
cmakelists: fixed tests to avoid clang warnings (#10705) * clang/"dead assignment" * clang/"Uninitialized argument value"
2019-08-07 12:49:33 +02:00
int a = 42;
CMake: Feature-detect __builtin_{add,sub}_overflow
2019-01-08 22:00:52 +01:00
__builtin_add_overflow(a, a, &a);
__builtin_sub_overflow(a, a, &a);
return 0;
}
" HAVE_BUILTIN_ADD_OVERFLOW)
MSVC: use MSVC instead of GCC-like compiler flags. - We can build with /W4, but it gives thousands of warnings. - _CRT_NONSTDC_NO_DEPRECATE disables warnings about POSIX functions. https://msdn.microsoft.com/en-us/library/ms235384.aspx - _CRT_SECURE_NO_WARNINGS https://msdn.microsoft.com/en-us/library/8ef0s5kh.aspx
2015-08-28 04:00:09 +02:00
if(MSVC)
# XXX: /W4 gives too many warnings. #3241
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(/W3)
add_definitions(-D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE)
build/msvc: Add missing WIN32 macro MSVC predefines `_WIN32`, but not `WIN32`. Also, some unnecessary includes have been removed.
2018-03-05 00:44:23 +01:00
add_definitions(-DWIN32)
MSVC: use MSVC instead of GCC-like compiler flags. - We can build with /W4, but it gives thousands of warnings. - _CRT_NONSTDC_NO_DEPRECATE disables warnings about POSIX functions. https://msdn.microsoft.com/en-us/library/ms235384.aspx - _CRT_SECURE_NO_WARNINGS https://msdn.microsoft.com/en-us/library/8ef0s5kh.aspx
2015-08-28 04:00:09 +02:00
else()
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-Wall -Wextra -pedantic -Wno-unused-parameter
build: -Wmissing-prototypes ref #343 Though I don't see a strong benefit, it isn't too much of a burden, and maybe avoids confusion in some cases.
2019-01-30 02:26:12 +01:00
-Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion
-Wmissing-prototypes)
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-28 02:20:27 +01:00
Detect support for and use -Wimplicit-fallthrough
2017-05-03 05:58:04 +02:00
check_c_compiler_flag(-Wimplicit-fallthrough HAS_WIMPLICIT_FALLTHROUGH_FLAG)
if(HAS_WIMPLICIT_FALLTHROUGH_FLAG)
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-Wimplicit-fallthrough)
Detect support for and use -Wimplicit-fallthrough
2017-05-03 05:58:04 +02:00
endif()
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-28 02:20:27 +01:00
# On FreeBSD 64 math.h uses unguarded C11 extension, which taints clang
# 3.4.1 used there.
build: FreeBSD: Disable -Wc11-extensions only for clang From FreeBSD ports patch: https://svnweb.freebsd.org/ports/head/editors/neovim/files/patch-CMakeLists.txt?revision=425833&view=markup References #4363
2017-05-21 13:44:02 +02:00
if(CMAKE_SYSTEM_NAME STREQUAL "FreeBSD" AND CMAKE_C_COMPILER_ID MATCHES "Clang")
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-Wno-c11-extensions)
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-28 02:20:27 +01:00
endif()
MSVC: use MSVC instead of GCC-like compiler flags. - We can build with /W4, but it gives thousands of warnings. - _CRT_NONSTDC_NO_DEPRECATE disables warnings about POSIX functions. https://msdn.microsoft.com/en-us/library/ms235384.aspx - _CRT_SECURE_NO_WARNINGS https://msdn.microsoft.com/en-us/library/8ef0s5kh.aspx
2015-08-28 04:00:09 +02:00
endif()
cmake: Build with -fstack-protector-strong if available #2597 If not available, fall back to -fstack-protector + --param=ssp-buffer-size=4 If that isn't available, do nothing. See the following articles for more information: https://lwn.net/Articles/584225/ https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/
2015-08-27 00:00:33 +02:00
if(MINGW)
Mingw: Use POSIX compatible stdio #3232 - There are some differences between stdio (*printf) functions in POSIX and the MS runtime, this commit enables Mingw compatibility for these functions
2014-07-03 15:32:09 +02:00
# Use POSIX compatible stdio in Mingw
add_definitions(-D__USE_MINGW_ANSI_STDIO)
build/msvc: Add missing WIN32 macro MSVC predefines `_WIN32`, but not `WIN32`. Also, some unnecessary includes have been removed.
2018-03-05 00:44:23 +01:00
endif()
if(WIN32)
# Windows Vista is the minimum supported version
MinGW: libuv needs -D_WIN32_WINNT=0x0600 Without this compilation fails due to a missing symbol: SRWLOCK in libuv headers. _WIN32_WINNT defines the Windows header version that is to be used, and it seems libuv requires this version. See https://github.com/joyent/libuv/commit/b471b33da88da0ca0b913573370cc6919ec134e7
2015-02-03 14:31:33 +01:00
add_definitions(-D_WIN32_WINNT=0x0600)
Mingw: Use POSIX compatible stdio #3232 - There are some differences between stdio (*printf) functions in POSIX and the MS runtime, this commit enables Mingw compatibility for these functions
2014-07-03 15:32:09 +02:00
endif()
Turn off -Werror by default. It inteferes with development activities by breaking your build in the middle of a refactor. Instead, let's enable -Werror on the Travis CI builds via a TRAVIS_CI_BUILD option.
2014-05-15 01:08:41 +02:00
build: Check if compiler supports -Wvla before use OpenBSD's GCC (4.2.1) doesn't have the -Wvla flag.
2015-10-02 18:51:45 +02:00
# OpenBSD's GCC (4.2.1) doesn't have -Wvla
check_c_compiler_flag(-Wvla HAS_WVLA_FLAG)
if(HAS_WVLA_FLAG)
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-Wvla)
build: Check if compiler supports -Wvla before use OpenBSD's GCC (4.2.1) doesn't have the -Wvla flag.
2015-10-02 18:51:45 +02:00
endif()
MinGW: don't use -fstack-protector Mingw-w64 fails to link when using -fstack-protector flags, disabled the flag check for non Unix system.
2015-10-14 01:46:32 +02:00
if(UNIX)
# -fstack-protector breaks non Unix builds even in Mingw-w64
check_c_compiler_flag(-fstack-protector-strong HAS_FSTACK_PROTECTOR_STRONG_FLAG)
check_c_compiler_flag(-fstack-protector HAS_FSTACK_PROTECTOR_FLAG)
if(HAS_FSTACK_PROTECTOR_STRONG_FLAG)
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-fstack-protector-strong)
MinGW: don't use -fstack-protector Mingw-w64 fails to link when using -fstack-protector flags, disabled the flag check for non Unix system.
2015-10-14 01:46:32 +02:00
elseif(HAS_FSTACK_PROTECTOR_FLAG)
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-fstack-protector --param ssp-buffer-size=4)
MinGW: don't use -fstack-protector Mingw-w64 fails to link when using -fstack-protector flags, disabled the flag check for non Unix system.
2015-10-14 01:46:32 +02:00
endif()
cmake: Build with -fstack-protector-strong if available #2597 If not available, fall back to -fstack-protector + --param=ssp-buffer-size=4 If that isn't available, do nothing. See the following articles for more information: https://lwn.net/Articles/584225/ https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/
2015-08-27 00:00:33 +02:00
endif()
cmake: Enable -fdiagnostics-color=auto gcc flag. #3137
2015-08-27 09:56:46 +02:00
check_c_compiler_flag(-fdiagnostics-color=auto HAS_DIAG_COLOR_FLAG)
if(HAS_DIAG_COLOR_FLAG)
build: use -fdiagnostics-color=always with Ninja (#10419) "auto" does not work, since Ninja does not appear as a TTY to gcc/clang, but handles stripping escape codes itself when output is not to a TTY. Ref: https://github.com/ninja-build/ninja/blob/ca041d88f4d6/src/build.cc#L158-L169
2019-07-04 15:24:33 +02:00
if(CMAKE_GENERATOR MATCHES "Ninja")
add_compile_options(-fdiagnostics-color=always)
else()
add_compile_options(-fdiagnostics-color=auto)
endif()
cmake: Enable -fdiagnostics-color=auto gcc flag. #3137
2015-08-27 09:56:46 +02:00
endif()
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
option(TRAVIS_CI_BUILD "Travis/QuickBuild CI, extra flags will be set" OFF)
Turn off -Werror by default. It inteferes with development activities by breaking your build in the middle of a refactor. Instead, let's enable -Werror on the Travis CI builds via a TRAVIS_CI_BUILD option.
2014-05-15 01:08:41 +02:00
if(TRAVIS_CI_BUILD)
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(STATUS "Travis/QuickBuild CI build enabled")
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-Werror)
ci: Force unsigned char usage for the 32bit build Since C leaves whether char is signed or unsigned up to the implementer, there are different defaults on different architectures. Forcing unsigned char for one of our CI builds should help catch these issues moving forward.
2016-10-09 19:55:08 +02:00
if(DEFINED ENV{BUILD_32BIT})
# Get some test coverage for unsigned char
build: CMake: do not set CMP0059 to old (#10363) Keeps using add_definitions for compatibility with older CMake. Newer CMake (3.12) would have `add_compile_definitions`, but it is not required, since `add_defitions` was meant to be used for compile/preprocessor definitions initially anyway. Ref: https://github.com/neovim/neovim/pull/4389
2019-06-29 20:37:48 +02:00
add_compile_options(-funsigned-char)
ci: Force unsigned char usage for the 32bit build Since C leaves whether char is signed or unsigned up to the implementer, there are different defaults on different architectures. Forcing unsigned char for one of our CI builds should help catch these issues moving forward.
2016-10-09 19:55:08 +02:00
endif()
Turn off -Werror by default. It inteferes with development activities by breaking your build in the middle of a refactor. Instead, let's enable -Werror on the Travis CI builds via a TRAVIS_CI_BUILD option.
2014-05-15 01:08:41 +02:00
endif()
Use CMAKE_C_FLAGS variable to set compiler flags. If the compiler is some GNU-alike variant, set the compiler flags to use the gnu99 dialect of C and enable all warnings. Non-GNU compilers may have to have their own magic added to set dialect and enable warnings. Closes #179.
2014-02-27 13:27:20 +01:00
eval/typval: Log list actions New logging is guarded by cmake LOG_LIST_ACTIONS define. To make it more efficient it is allocated as a linked list with chunks of length 2^(7+chunk_num); that uses basically the same idea as behind increasing kvec length (make appending O(1) (amortized)), but reduces constant by not bothering to move memory around what realloc() would surely do: it is not like we need random access to log entries here to justify usage of a single continuous memory block.
2018-01-03 02:25:42 +01:00
option(LOG_LIST_ACTIONS "Add list actions logging" OFF)
CMake: Set custom RelWithDebInfo compile flags.
2014-11-08 12:49:04 +01:00
add_definitions(-DINCLUDE_GENERATED_DECLARATIONS)
cmake: Explicitly declare C as the project language There's a mix of CXX and C related variables being set/referenced in our CMake files. Since we only use C, use an explicit language list of "C" instead of the implicit "C CXX" and replace all uses of CXX variables with their C counterparts
2018-06-15 14:33:07 +02:00
if(CMAKE_C_COMPILER_ID STREQUAL "GNU" OR CMAKE_C_COMPILER_ID STREQUAL "Clang")
cmake: Consolidate enabling of "undefined symbol" errors
2018-06-16 16:18:55 +02:00
if(CMAKE_SYSTEM_NAME STREQUAL "SunOS")
set(NO_UNDEFINED "-Wl,--no-undefined -lsocket")
elseif(NOT CMAKE_SYSTEM_NAME STREQUAL "Darwin")
set(NO_UNDEFINED "-Wl,--no-undefined")
endif()
set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} ${NO_UNDEFINED}")
set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} ${NO_UNDEFINED}")
cmake: Linux: define _GNU_SOURCE. Closes #4042
2016-01-25 03:16:00 +01:00
# For O_CLOEXEC, O_DIRECTORY, and O_NOFOLLOW flags on older systems
# (pre POSIX.1-2008: glibc 2.11 and earlier). #4042
api: list information about all channels/jobs. Fire autocmd when channel opens or its info changes. Add a way for API clients can describe themselves.
2017-05-14 07:43:07 +02:00
# For ptsname(). #6743
cmake: Linux: define _GNU_SOURCE. Closes #4042
2016-01-25 03:16:00 +01:00
add_definitions(-D_GNU_SOURCE)
Don't allow undefined references under Linux. Many other systems expect this already, but on Linux the default is to allow them. Let's turn that off.
2014-05-15 03:14:28 +02:00
endif()
Add missing linker flags required for LuaJIT on 64-bit Mac OS X. This was brought up in #1294.
2014-10-17 12:50:13 +02:00
if(CMAKE_SYSTEM_NAME STREQUAL "Darwin" AND CMAKE_SIZEOF_VOID_P EQUAL 8)
# Required for luajit.
set(CMAKE_EXE_LINKER_FLAGS
"${CMAKE_EXE_LINKER_FLAGS} -pagezero_size 10000 -image_base 100000000")
set(CMAKE_SHARED_LINKER_FLAGS
"${CMAKE_SHARED_LINKER_FLAGS} -image_base 100000000")
set(CMAKE_MODULE_LINKER_FLAGS
"${CMAKE_MODULE_LINKER_FLAGS} -image_base 100000000")
endif()
Fix #451: Build broken on OSX. Problem: Build breaks in OSX if macports ncurses present, due to header conflict involving 'term.h'. Solution: Modify include search order.
2014-04-03 21:00:43 +02:00
include_directories("${PROJECT_BINARY_DIR}/config")
include_directories("${PROJECT_SOURCE_DIR}/src")
build: LibUV: required version: 1.28.0 (#10456) For uv_gettimeofday.
2019-07-09 18:55:16 +02:00
find_package(LibUV 1.28.0 REQUIRED)
Tell cmake to use `-isystem` third-party includes This adds the `SYSTEM` parameter to `include_directories`, which will tell cmake to use `-isystem` instead of `-I` for specifying include directories. One advantage is that compilers won't emit warnings for included files that belong to dependencies.
2014-05-15 13:21:13 +02:00
include_directories(SYSTEM ${LIBUV_INCLUDE_DIRS})
Fix #451: Build broken on OSX. Problem: Build breaks in OSX if macports ncurses present, due to header conflict involving 'term.h'. Solution: Modify include search order.
2014-04-03 21:00:43 +02:00
cmake: msgpack: Add more thorough version check In 33bc332, version constraints were added to pkg_search_module(), but that only affects the set of directories searched by find_library()/find_path(). Once the header directory is found, parse the version from version_master.h so it can be checked by the find_package() call in the root CMakeLists.txt.
2016-02-05 04:21:51 +01:00
find_package(Msgpack 1.0.0 REQUIRED)
Tell cmake to use `-isystem` third-party includes This adds the `SYSTEM` parameter to `include_directories`, which will tell cmake to use `-isystem` instead of `-I` for specifying include directories. One advantage is that compilers won't emit warnings for included files that belong to dependencies.
2014-05-15 13:21:13 +02:00
include_directories(SYSTEM ${MSGPACK_INCLUDE_DIRS})
Add cmake module for finding msgpack
2014-04-10 20:39:34 +02:00
build: LibLUV: update required version [ci skip] (#10381) Required after d33aaa0f5. Does not really make a difference, since the VERSION is not handled with our FindLibLUV (due to missing pkg-config information (https://github.com/luvit/luv/issues/354)).
2019-07-01 03:26:05 +02:00
find_package(LibLUV 1.30.0 REQUIRED)
lua: introduce vim.loop (expose libuv event-loop) #10123 Co-authored-by: Andrey Popp <8mayday@gmail.com> closes #9546 closes #10084
2019-06-10 14:13:18 +02:00
include_directories(SYSTEM ${LIBLUV_INCLUDE_DIRS})
cmake: use LibFindMacros for utf8proc (#11114) Also update doc.
2019-09-29 04:44:02 +02:00
find_package(UTF8PROC REQUIRED)
Create BuildUtf8proc.cmake and FindUtf8proc.cmake Using advanced search and replace technology
2019-06-06 14:13:10 +02:00
include_directories(SYSTEM ${UTF8PROC_INCLUDE_DIRS})
if(WIN32)
add_definitions(-DUTF8PROC_STATIC)
endif()
cmake: Support building without LuaJIT. #6736 Compile `nvim` executable against Lua if PREFER_LUA=ON. As the testing library `nvim-test` requires LuaJIT, it is still compiled against LuaJIT. If LuaJIT is not available, `nvim-test` is not built.
2017-05-13 13:57:08 +02:00
# Note: The test lib requires LuaJIT; it will be skipped if LuaJIT is missing.
option(PREFER_LUA "Prefer Lua over LuaJIT in the nvim executable." OFF)
cmake: Allow switching from luajit to lua
2017-01-21 00:33:09 +01:00
cmake: Support building without LuaJIT. #6736 Compile `nvim` executable against Lua if PREFER_LUA=ON. As the testing library `nvim-test` requires LuaJIT, it is still compiled against LuaJIT. If LuaJIT is not available, `nvim-test` is not built.
2017-05-13 13:57:08 +02:00
if(PREFER_LUA)
build: relax find_package() version spec We need a way to say "Lua 5.1.x" is required. "5.1 EXACT" does not match 5.1.5, so it's useless. https://github.com/neovim/neovim/pull/9197#discussion_r230962070
2018-11-06 01:48:49 +01:00
find_package(Lua 5.1 REQUIRED)
cmake: Support building without LuaJIT. #6736 Compile `nvim` executable against Lua if PREFER_LUA=ON. As the testing library `nvim-test` requires LuaJIT, it is still compiled against LuaJIT. If LuaJIT is not available, `nvim-test` is not built.
2017-05-13 13:57:08 +02:00
set(LUA_PREFERRED_INCLUDE_DIRS ${LUA_INCLUDE_DIR})
set(LUA_PREFERRED_LIBRARIES ${LUA_LIBRARIES})
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
# Passive (not REQUIRED): if LUAJIT_FOUND is not set, nvim-test is skipped.
cmake: Support building without LuaJIT. #6736 Compile `nvim` executable against Lua if PREFER_LUA=ON. As the testing library `nvim-test` requires LuaJIT, it is still compiled against LuaJIT. If LuaJIT is not available, `nvim-test` is not built.
2017-05-13 13:57:08 +02:00
find_package(LuaJit)
else()
find_package(LuaJit REQUIRED)
set(LUA_PREFERRED_INCLUDE_DIRS ${LUAJIT_INCLUDE_DIRS})
set(LUA_PREFERRED_LIBRARIES ${LUAJIT_LIBRARIES})
cmake: Allow switching from luajit to lua
2017-01-21 00:33:09 +01:00
endif()
eval: Add luaeval function No tests yet, no documentation update, no :lua* stuff, no vim module. converter.c should also work with typval_T, not Object. Known problem: luaeval("1", {}) results in PANIC: unprotected error in call to Lua API (attempt to index a nil value) Ref #3823
2016-03-04 19:55:28 +01:00
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 17:05:48 +02:00
list(APPEND CMAKE_REQUIRED_INCLUDES "${MSGPACK_INCLUDE_DIRS}")
check_c_source_compiles("
#include <msgpack.h>
int
main(void)
{
return MSGPACK_OBJECT_FLOAT32;
}
" MSGPACK_HAS_FLOAT32)
build: FindLibIntl: fix warning about CMP0075 (#10427) * build: FindLibIntl: fix warning about CMP0075 The common pattern elsewhere to set this only during the check, and here it was not unset, resulting in a warning later (on Alpine 3.10): -- Found Iconv -- Looking for pthread.h CMake Warning (dev) at /usr/share/cmake/Modules/CheckIncludeFile.cmake:80 (message): Policy CMP0075 is not set: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. Run "cmake --help-policy CMP0075" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMAKE_REQUIRED_LIBRARIES is set to: /usr/lib/libintl.so For compatibility with CMake 3.11 and below this check is ignoring it. Call Stack (most recent call first): /usr/share/cmake/Modules/FindThreads.cmake:105 (CHECK_INCLUDE_FILE) CMakeLists.txt:482 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Looking for pthread.h - found * build: remove lists / REMOVE_ITEM around check_c_source_compiles
2019-07-05 12:19:13 +02:00
list(REMOVE_ITEM CMAKE_REQUIRED_INCLUDES "${MSGPACK_INCLUDE_DIRS}")
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 17:05:48 +02:00
if(MSGPACK_HAS_FLOAT32)
cmake: Prefer add_definitions() for setting preprocessor defines
2018-06-18 05:29:39 +02:00
add_definitions(-DNVIM_MSGPACK_HAS_FLOAT32)
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 17:05:48 +02:00
endif()
win: Terminal UI #6315 For CI builds unibilium is provided through msys2 packages, and libtermkey is built from source in third-party from equalsraf/libtermkey. In Windows we cannot read terminal input from the stdin file descriptor, instead use libuv's uv_tty API. It should handle key input and encoding. The UI suspend is not implemented for Windows, because the SIGSTP/SIGCONT do not exist in windows. Currently this is a NOOP. Closes #3902 Closes #6640
2017-03-18 01:06:47 +01:00
option(FEAT_TUI "Enable the Terminal UI" ON)
ui: Rewrite the builtin terminal UI Now all terminal-handling code was moved to src/nvim/tui, which implements a new terminal UI based on libtermkey and unibilium
2015-02-13 16:06:05 +01:00
Windows: Don't build the TUI is systems where it is not supported The TUI can be enabled/disabled at build time with -DFEAT_TUI, default is ON for UNIX, and OFF for non UNIX. When off, Neovim prints a message to stderr, along with a list of the server endpoints.
2016-05-23 23:16:39 +02:00
if(FEAT_TUI)
build: rename CMake find modules for LibFindMacros #10928 We are using "LIBFOO" prefixes for `LIBFOO_INCLUDE_DIRS` etc, and therefore need to use this for the PREFIX with LibFindMacros also, so that `"${${PREFIX}_FIND_VERSION}"` gets handled there properly. The alternative would be to either manually handle/set the upper/mixed case variants of those variable additionally, which is not as easy. Keeping the existing names is useful for packagers. Before this the version requirements with `find_package(Unibilium 2.0 REQUIRED)` was not handled (a49cf5126), and it prepares for using a required version with libvterm (initially/wrongly ported in 1896c72a5).
2019-09-06 23:39:41 +02:00
find_package(UNIBILIUM 2.0 REQUIRED)
Windows: Don't build the TUI is systems where it is not supported The TUI can be enabled/disabled at build time with -DFEAT_TUI, default is ON for UNIX, and OFF for non UNIX. When off, Neovim prints a message to stderr, along with a list of the server endpoints.
2016-05-23 23:16:39 +02:00
include_directories(SYSTEM ${UNIBILIUM_INCLUDE_DIRS})
tui: Use unibi_var_from_num when available As of unibilium 1.2.1, directly manipulating unibi_var_t is deprecated. ../src/nvim/tui/tui.c: In function 'update_attrs': ../src/nvim/tui/tui.c:321:7: warning: 'i' is deprecated: use unibi_var_from_num or unibi_num_from_var instead [-Wdeprecated-declarations] data->params[0].i = (fg >> 16) & 0xff; // red ^~~~ In file included from ../src/nvim/tui/tui.c:12:0: /usr/include/unibilium.h:632:9: note: declared here int i UNIBI_DEPRECATED("use unibi_var_from_num or unibi_num_from_var instead"); ^ All use should go through unibi_{num,str}_from_var and unibi_var_from_{num,str}. Wrap access of unibi_var_t behind a new UNIBI_SET_NUM_VAR macro which uses the new functions when they're available.
2017-09-17 05:13:35 +02:00
list(APPEND CMAKE_REQUIRED_INCLUDES "${UNIBILIUM_INCLUDE_DIRS}")
list(APPEND CMAKE_REQUIRED_LIBRARIES "${UNIBILIUM_LIBRARIES}")
check_c_source_compiles("
#include <unibilium.h>
int
main(void)
{
return unibi_num_from_var(unibi_var_from_num(0));
}
" UNIBI_HAS_VAR_FROM)
build: FindLibIntl: fix warning about CMP0075 (#10427) * build: FindLibIntl: fix warning about CMP0075 The common pattern elsewhere to set this only during the check, and here it was not unset, resulting in a warning later (on Alpine 3.10): -- Found Iconv -- Looking for pthread.h CMake Warning (dev) at /usr/share/cmake/Modules/CheckIncludeFile.cmake:80 (message): Policy CMP0075 is not set: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. Run "cmake --help-policy CMP0075" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMAKE_REQUIRED_LIBRARIES is set to: /usr/lib/libintl.so For compatibility with CMake 3.11 and below this check is ignoring it. Call Stack (most recent call first): /usr/share/cmake/Modules/FindThreads.cmake:105 (CHECK_INCLUDE_FILE) CMakeLists.txt:482 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Looking for pthread.h - found * build: remove lists / REMOVE_ITEM around check_c_source_compiles
2019-07-05 12:19:13 +02:00
list(REMOVE_ITEM CMAKE_REQUIRED_INCLUDES "${UNIBILIUM_INCLUDE_DIRS}")
list(REMOVE_ITEM CMAKE_REQUIRED_LIBRARIES "${UNIBILIUM_LIBRARIES}")
tui: Use unibi_var_from_num when available As of unibilium 1.2.1, directly manipulating unibi_var_t is deprecated. ../src/nvim/tui/tui.c: In function 'update_attrs': ../src/nvim/tui/tui.c:321:7: warning: 'i' is deprecated: use unibi_var_from_num or unibi_num_from_var instead [-Wdeprecated-declarations] data->params[0].i = (fg >> 16) & 0xff; // red ^~~~ In file included from ../src/nvim/tui/tui.c:12:0: /usr/include/unibilium.h:632:9: note: declared here int i UNIBI_DEPRECATED("use unibi_var_from_num or unibi_num_from_var instead"); ^ All use should go through unibi_{num,str}_from_var and unibi_var_from_{num,str}. Wrap access of unibi_var_t behind a new UNIBI_SET_NUM_VAR macro which uses the new functions when they're available.
2017-09-17 05:13:35 +02:00
if(UNIBI_HAS_VAR_FROM)
cmake: Prefer add_definitions() for setting preprocessor defines
2018-06-18 05:29:39 +02:00
add_definitions(-DNVIM_UNIBI_HAS_VAR_FROM)
tui: Use unibi_var_from_num when available As of unibilium 1.2.1, directly manipulating unibi_var_t is deprecated. ../src/nvim/tui/tui.c: In function 'update_attrs': ../src/nvim/tui/tui.c:321:7: warning: 'i' is deprecated: use unibi_var_from_num or unibi_num_from_var instead [-Wdeprecated-declarations] data->params[0].i = (fg >> 16) & 0xff; // red ^~~~ In file included from ../src/nvim/tui/tui.c:12:0: /usr/include/unibilium.h:632:9: note: declared here int i UNIBI_DEPRECATED("use unibi_var_from_num or unibi_num_from_var instead"); ^ All use should go through unibi_{num,str}_from_var and unibi_var_from_{num,str}. Wrap access of unibi_var_t behind a new UNIBI_SET_NUM_VAR macro which uses the new functions when they're available.
2017-09-17 05:13:35 +02:00
endif()
build: dependencies: specify minimum versions
2018-11-03 21:28:07 +01:00
find_package(LibTermkey 0.18 REQUIRED)
Windows: Don't build the TUI is systems where it is not supported The TUI can be enabled/disabled at build time with -DFEAT_TUI, default is ON for UNIX, and OFF for non UNIX. When off, Neovim prints a message to stderr, along with a list of the server endpoints.
2016-05-23 23:16:39 +02:00
include_directories(SYSTEM ${LIBTERMKEY_INCLUDE_DIRS})
endif()
ui: Rewrite the builtin terminal UI Now all terminal-handling code was moved to src/nvim/tui, which implements a new terminal UI based on libtermkey and unibilium
2015-02-13 16:06:05 +01:00
build: dependencies: specify minimum libvterm (#10997) libvterm now advertises a version number, so we can specify the minimum required version. And this is necessary because there were breaking changes in its API. ref 2a590e229363 ref https://github.com/neovim/neovim/issues/10991
2019-09-12 03:25:25 +02:00
find_package(LIBVTERM 0.1 REQUIRED)
deps: Add libvterm to the project dependencies libvterm is a terminal emulation library with abstract display. It will be used to implement builtin terminal emulation into Nvim.
2015-02-28 14:41:53 +01:00
include_directories(SYSTEM ${LIBVTERM_INCLUDE_DIRS})
win: integrate winpty (WIP) Handling of process exit is still broken. It detects the moment when the child process exits, then quickly stops polling for process output. It should continue polling for output until the agent has scraped all of the process' output. This problem is easy to notice by running a command like "dir && exit", but even typing "exit<ENTER>" can manifest the problem -- the "t" might not appear. winpty's Cygwin adapter handles shutdown by waiting for the agent to close the CONOUT pipe, which it does after it has scraped the child's last output. AFAIK, neovim doesn't do anything interesting when winpty closes the CONOUT pipe.
2016-02-24 09:14:19 +01:00
if(WIN32)
build: dependencies: specify minimum versions
2018-11-03 21:28:07 +01:00
find_package(Winpty 0.4.3 REQUIRED)
win: integrate winpty (WIP) Handling of process exit is still broken. It detects the moment when the child process exits, then quickly stops polling for process output. It should continue polling for output until the agent has scraped all of the process' output. This problem is easy to notice by running a command like "dir && exit", but even typing "exit<ENTER>" can manifest the problem -- the "t" might not appear. winpty's Cygwin adapter handles shutdown by waiting for the agent to close the CONOUT pipe, which it does after it has scraped the child's last output. AFAIK, neovim doesn't do anything interesting when winpty closes the CONOUT pipe.
2016-02-24 09:14:19 +01:00
include_directories(SYSTEM ${WINPTY_INCLUDE_DIRS})
endif()
CMake: Add option for Clang TSan, rename option ASAN -> ASAN_UBSAN.
2015-06-09 10:43:22 +02:00
option(CLANG_ASAN_UBSAN "Enable Clang address & undefined behavior sanitizer for nvim binary." OFF)
CMake: Add option for Clang MSan.
2015-06-08 18:49:23 +02:00
option(CLANG_MSAN "Enable Clang memory sanitizer for nvim binary." OFF)
CMake: Add option for Clang TSan, rename option ASAN -> ASAN_UBSAN.
2015-06-09 10:43:22 +02:00
option(CLANG_TSAN "Enable Clang thread sanitizer for nvim binary." OFF)
if((CLANG_ASAN_UBSAN AND CLANG_MSAN)
OR (CLANG_ASAN_UBSAN AND CLANG_TSAN)
OR (CLANG_MSAN AND CLANG_TSAN))
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(FATAL_ERROR "Sanitizers cannot be enabled simultaneously")
CMake: Add option for Clang MSan.
2015-06-08 18:49:23 +02:00
endif()
CMake: Add option for Clang TSan, rename option ASAN -> ASAN_UBSAN.
2015-06-09 10:43:22 +02:00
if((CLANG_ASAN_UBSAN OR CLANG_MSAN OR CLANG_TSAN) AND NOT CMAKE_C_COMPILER_ID MATCHES "Clang")
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(FATAL_ERROR "Sanitizers are only supported for Clang")
deps: Add jemalloc as an optional dependency Jemalloc will be used if the cmake option `USE_JEMALLOC` is enabled(which is the default). To avoid trouble with clang's ASAN, it is disabled by default if the `SANITIZE` option is enabled. Since jemalloc has thread cache for small objects, it fills the gap created by removing klib memory pools. The `xstrdup` funciton(memory.c) had to be reimplemented on top of `xmalloc` to make it work with a custom allocator.
2015-04-12 16:40:08 +02:00
endif()
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
if(ENABLE_LIBINTL)
# LibIntl (not Intl) selects our FindLibIntl.cmake script. #8464
find_package(LibIntl REQUIRED)
build: use the proper libintl include variable What was there worked, but it wasn't meant to be the variable that you use for inclusion.
2014-11-08 22:09:47 +01:00
include_directories(SYSTEM ${LibIntl_INCLUDE_DIRS})
Fix #451: Build broken on OSX. Problem: Build breaks in OSX if macports ncurses present, due to header conflict involving 'term.h'. Solution: Modify include search order.
2014-04-03 21:00:43 +02:00
endif()
build/CMake: find_package(… REQUIRED) "Always use `find_package` with `REQUIRED`." - We make an exception for LuaJit (not REQUIRED): the `nvim-test` target is included only if we can find LuaJit. This is partially a cargo-cult (reference below), but it uncovered at least one problem: `find_package(LibIntl REQUIRED)` fails on my vanilla ubuntu 16.04 system. ref: https://schneide.blog/2017/11/06/4-tips-for-better-cmake/ > optional dependencies is nice, but skipping on REQUIRED is not the way > you want to do it. In the worst case, some of your features will just > not work if those packages are not found, with no explanation > whatsoever. Instead, use explicit feature-toggles (e.g. using option()) > that either skip the find_package call or use it with REQUIRED, so the > user will know that another lib is needed for this feature.
2018-06-01 20:17:24 +02:00
if(ENABLE_LIBICONV)
find_package(Iconv REQUIRED)
build: pull iconv detection into its own FindIconv.cmake file This will provide better control for those who may want to alter which one gets used.
2014-11-08 22:18:04 +01:00
include_directories(SYSTEM ${Iconv_INCLUDE_DIRS})
Fix #451: Build broken on OSX. Problem: Build breaks in OSX if macports ncurses present, due to header conflict involving 'term.h'. Solution: Modify include search order.
2014-04-03 21:00:43 +02:00
endif()
use CMake's built in pthread detection CMake ships with a standard FindThreads module which can be used to a) test for a threading library and b) confirm that it is pthread. It also allows the hard-coding of the threading library name to be removed from ``src/CMakeLists.txt``. Make it an error not to have a pthread library installed and indicate to CMake that we strongly prefer pthread to any other platform threading library.
2014-02-24 19:52:12 +01:00
# Determine platform's threading library. Set CMAKE_THREAD_PREFER_PTHREAD
Remove pthread fatal check from CMakeLists.txt #891
2014-06-25 23:47:27 +02:00
# explicitly to indicate a strong preference for pthread.
use CMake's built in pthread detection CMake ships with a standard FindThreads module which can be used to a) test for a threading library and b) confirm that it is pthread. It also allows the hard-coding of the threading library name to be removed from ``src/CMakeLists.txt``. Make it an error not to have a pthread library installed and indicate to CMake that we strongly prefer pthread to any other platform threading library.
2014-02-24 19:52:12 +01:00
set(CMAKE_THREAD_PREFER_PTHREAD ON)
find_package(Threads REQUIRED)
Fix build output paths for Visual Studio generator The Visual Studio cmake generator creates subdirectories inside the build path for different build configuration. But this breaks some of our cmake scripts, like the help tags installer, that assume the targets are built in that location. Updated CMakeLists.txt to remove extra paths.
2016-01-09 03:40:57 +01:00
# Place targets in bin/ or lib/ for all build configurations
Revamp the build system. This achieves several goals: * Less reliance on scripts so we have better portability to Windows (though we still have a ways to go for proper Windows support). Luajit, luarocks, moonscript, and busted are all installed via CMake now. * Trying to make use of pkg-config to get the correct libraries. The latest libuv is still broken in this regard, but we'll at least be in a position to use it. * Allow the use of Ninja or make. The former runs faster in many environments, and automatically makes use of parallel builds. This also allows for system installed dependencies--though not through the Makefile just yet--and adds support for FreeBSD. This also make us build libuv and luajit as static libraries only, since we're only concerned about having static libraries for our bundled dependencies.
2014-03-03 16:09:06 +01:00
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
Allow building as a static -fPIC library
2014-12-01 03:22:46 +01:00
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
Fix build output paths for Visual Studio generator The Visual Studio cmake generator creates subdirectories inside the build path for different build configuration. But this breaks some of our cmake scripts, like the help tags installer, that assume the targets are built in that location. Updated CMakeLists.txt to remove extra paths.
2016-01-09 03:40:57 +01:00
foreach(CFGNAME ${CMAKE_CONFIGURATION_TYPES})
string(TOUPPER ${CFGNAME} CFGNAME)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY_${CFGNAME} ${CMAKE_BINARY_DIR}/bin)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY_${CFGNAME} ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY_${CFGNAME} ${CMAKE_BINARY_DIR}/lib)
endforeach()
Changed binary output directory from src/ to bin/
2014-02-22 16:30:50 +01:00
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
# Find Lua interpreter
Refactor the lua dependency checking. This is in preparation for the next step, which is to find a suitable lua interpreter, rather than just erroring when an interpreter is found but doesn't have the necessary dependencies. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:10 +02:00
include(LuaHelpers)
Update lua client to 0.0.1-24 The new version of the lua client uses libmpack as a backend, and some test scripts had to be updated to reflect that.
2016-04-13 14:21:32 +02:00
set(LUA_DEPENDENCIES lpeg mpack bit)
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
if(NOT LUA_PRG)
CMake: Search all possibly usable Lua executables. (#4858)
2016-06-03 18:21:29 +02:00
foreach(CURRENT_LUA_PRG luajit lua5.1 lua5.2 lua)
cmake: only set LUA_PRG with successful check (#11172) This is relevant for when using `USE_BUNDLED_LUAJIT=ON` with `USE_BUNDLED_LUAROCKS=OFF`, and then building without the necessary modules being installed/activated there yet: it would check the other (system) "lua" interpreters also, and in case all failed keep the `LUA_PRG` in the cache for the last failed entry - making it not re-check the previous ones on the next build (after you might have activated your custom LuaRocks installation). Only setting LUA_PRG if the check was successful handles the case better where it is configured already - we should not try to re-configure it then.
2019-10-07 17:42:40 +02:00
unset(_CHECK_LUA_PRG CACHE)
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
unset(LUA_PRG_WORKS)
cmake: only set LUA_PRG with successful check (#11172) This is relevant for when using `USE_BUNDLED_LUAJIT=ON` with `USE_BUNDLED_LUAROCKS=OFF`, and then building without the necessary modules being installed/activated there yet: it would check the other (system) "lua" interpreters also, and in case all failed keep the `LUA_PRG` in the cache for the last failed entry - making it not re-check the previous ones on the next build (after you might have activated your custom LuaRocks installation). Only setting LUA_PRG if the check was successful handles the case better where it is configured already - we should not try to re-configure it then.
2019-10-07 17:42:40 +02:00
find_program(_CHECK_LUA_PRG ${CURRENT_LUA_PRG})
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
cmake: only set LUA_PRG with successful check (#11172) This is relevant for when using `USE_BUNDLED_LUAJIT=ON` with `USE_BUNDLED_LUAROCKS=OFF`, and then building without the necessary modules being installed/activated there yet: it would check the other (system) "lua" interpreters also, and in case all failed keep the `LUA_PRG` in the cache for the last failed entry - making it not re-check the previous ones on the next build (after you might have activated your custom LuaRocks installation). Only setting LUA_PRG if the check was successful handles the case better where it is configured already - we should not try to re-configure it then.
2019-10-07 17:42:40 +02:00
if(_CHECK_LUA_PRG)
check_lua_deps(${_CHECK_LUA_PRG} "${LUA_DEPENDENCIES}" LUA_PRG_WORKS)
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
if(LUA_PRG_WORKS)
cmake: only set LUA_PRG with successful check (#11172) This is relevant for when using `USE_BUNDLED_LUAJIT=ON` with `USE_BUNDLED_LUAROCKS=OFF`, and then building without the necessary modules being installed/activated there yet: it would check the other (system) "lua" interpreters also, and in case all failed keep the `LUA_PRG` in the cache for the last failed entry - making it not re-check the previous ones on the next build (after you might have activated your custom LuaRocks installation). Only setting LUA_PRG if the check was successful handles the case better where it is configured already - we should not try to re-configure it then.
2019-10-07 17:42:40 +02:00
set(LUA_PRG "${_CHECK_LUA_PRG}" CACHE FILEPATH "Path to a program.")
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
break()
endif()
endif()
endforeach()
cmake: only set LUA_PRG with successful check (#11172) This is relevant for when using `USE_BUNDLED_LUAJIT=ON` with `USE_BUNDLED_LUAROCKS=OFF`, and then building without the necessary modules being installed/activated there yet: it would check the other (system) "lua" interpreters also, and in case all failed keep the `LUA_PRG` in the cache for the last failed entry - making it not re-check the previous ones on the next build (after you might have activated your custom LuaRocks installation). Only setting LUA_PRG if the check was successful handles the case better where it is configured already - we should not try to re-configure it then.
2019-10-07 17:42:40 +02:00
unset(_CHECK_LUA_PRG CACHE)
Check dependencies for each lua interpreter. - When USE_BUNDLED=OFF and the system has multiple lua interpreters (luajit AND lua) it may occur that only the later has the needed dependencies (lua-lpeg, lua-cmsgpack). If we pick luajit then finding the dependencies FAILS. - This commit groups detection of the lua interpreter with the lua dependencies it tries to find them for both the interpreters and choses the first one that has them. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:18 +02:00
else()
check_lua_deps(${LUA_PRG} "${LUA_DEPENDENCIES}" LUA_PRG_WORKS)
endif()
Add checks for lpeg/cmsgpack lua packages These checks will stop the build process with meaningful error messages if any of those packages are not installed.
2014-04-13 12:06:35 +02:00
Refactor the lua dependency checking. This is in preparation for the next step, which is to find a suitable lua interpreter, rather than just erroring when an interpreter is found but doesn't have the necessary dependencies. Helped-by: John Szakmeister <john@szakmeister.net>
2014-07-11 13:12:10 +02:00
if(NOT LUA_PRG_WORKS)
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(FATAL_ERROR "Failed to find a Lua 5.1-compatible interpreter")
Add checks for lpeg/cmsgpack lua packages These checks will stop the build process with meaningful error messages if any of those packages are not installed.
2014-04-13 12:06:35 +02:00
endif()
build: adjust some messages (#9087)
2018-10-06 18:45:34 +02:00
message(STATUS "Using Lua interpreter: ${LUA_PRG}")
Add checks for lpeg/cmsgpack lua packages These checks will stop the build process with meaningful error messages if any of those packages are not installed.
2014-04-13 12:06:35 +02:00
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
# Setup busted.
third-party: Build busted in Windows Busted now builds on Windows, remove the check. In Windows the binary is called busted.bat.
2016-03-19 18:54:14 +01:00
find_program(BUSTED_PRG NAMES busted busted.bat)
Add Lua 5.1 as a third party dep Also add a functionaltest-lua target to run the functional tests using the lua interpreter and corresponding helper to top-level Makefile
2016-03-07 04:42:49 +01:00
find_program(BUSTED_LUA_PRG busted-lua)
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
if(NOT BUSTED_OUTPUT_TYPE)
build: Default BUSTED_OUTPUT_TYPE to "nvim" (#6811)
2017-05-25 14:51:53 +02:00
set(BUSTED_OUTPUT_TYPE "nvim")
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
endif()
Revamp the build system. This achieves several goals: * Less reliance on scripts so we have better portability to Windows (though we still have a ways to go for proper Windows support). Luajit, luarocks, moonscript, and busted are all installed via CMake now. * Trying to make use of pkg-config to get the correct libraries. The latest libuv is still broken in this regard, but we'll at least be in a position to use it. * Allow the use of Ninja or make. The former runs faster in many environments, and automatically makes use of parallel builds. This also allows for system installed dependencies--though not through the Makefile just yet--and adds support for FreeBSD. This also make us build libuv and luajit as static libraries only, since we're only concerned about having static libraries for our bundled dependencies.
2014-03-03 16:09:06 +01:00
Tests: add luacheck for linting tests Source: https://github.com/mpeterv/luacheck Docs: http://luacheck.readthedocs.org/en/0.12.0/index.html Run via "make testlint".
2015-11-17 13:16:33 +01:00
find_program(LUACHECK_PRG luacheck)
ci: pylint target via flake8 Ref: https://github.com/neovim/neovim/pull/10631#issuecomment-515756591
2019-07-29 05:04:12 +02:00
find_program(FLAKE8_PRG flake8)
eval: use gperf to generate the hash of builtin functions make api functions highlighted as builtins in vim.vim
2016-06-19 16:41:08 +02:00
find_program(GPERF_PRG gperf)
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
include(InstallHelpers)
Build: Use GNUInstallDirs, install man pages #2649 For now, only install man pages matching "nvim*.1": we don't want to install xxd.1 as it might conflict with that of a user's Vim installation. closes #1826 Reviewed-by: Florian Walch <florian@fwalch.com> Helped-by: John Szakmeister <john@szakmeister.net>
2015-05-17 20:45:30 +02:00
file(GLOB MANPAGES
RELATIVE ${CMAKE_CURRENT_SOURCE_DIR}
Remove outdated and unused manuals #2891 `nvim-[lang].1`: The non-english manuals are completely outdated and still written in roff, as opposed to mdoc, which is used for `nvim.1`. Given that, they're nearly useless at the moment, and when/if they are updated, they should probably be rewritten from scratch using `nvim.1` as a reference. `xxd*.1`: xxd hasn't been in the source tree for a long time, so the manual is of little use. `nvimtutor*.1`: The vimtutor script hasn't ever shipped with nvim, and the consensus seems to be that it won't, at least in the form of an executable installed alongside `$(PREFIX)/bin/nvim` (see #2700). In `nvim.1`, the argument to the `.Os` macro was removed. This was done because its only purpose was to signify that nvim and nvimtutor were part of the "Neovim" distribution, i.e., one and the same, which isn't applicable anymore because `nvimtutor.1` is being removed. From the `.Os` documentation in `man mdoc`: Os Operating system version for display in the page footer. This is the mandatory third macro of any mdoc file. Its syntax is as follows: .Os [system [version]] The optional system parameter specifies the relevant operating system or environment. It is suggested to leave it unspecified, in which case mandoc(1) uses its -Ios argument or, if that isn't specified either, sysname and release as returned by uname(3). Examples: .Os .Os KTH/CSC/TCS .Os BSD 4.3 See also Dd and Dt. Reviewed-by: Felipe Morales <hel.sheep@gmail.com> Reviewed-by: Florian Walch <florian@fwalch.com> Reviewed-by: Justin M. Keyes <justinkz@gmail.com> [ci skip]
2015-06-24 20:12:51 +02:00
man/nvim.1)
Build: Use GNUInstallDirs, install man pages #2649 For now, only install man pages matching "nvim*.1": we don't want to install xxd.1 as it might conflict with that of a user's Vim installation. closes #1826 Reviewed-by: Florian Walch <florian@fwalch.com> Helped-by: John Szakmeister <john@szakmeister.net>
2015-05-17 20:45:30 +02:00
install_helper(
FILES ${MANPAGES}
DESTINATION ${CMAKE_INSTALL_MANDIR}/man1)
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
#
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
# Go down the tree.
build/CMakeLists.txt: group related logic - Group CMAKE_BUILD_TYPE-related logic together. - Print the MIN_LOG_LEVEL message (in the build-log) next to the CMAKE_BUILD_TYPE message.
2019-02-15 21:18:16 +01:00
#
Revamp the build system. This achieves several goals: * Less reliance on scripts so we have better portability to Windows (though we still have a ways to go for proper Windows support). Luajit, luarocks, moonscript, and busted are all installed via CMake now. * Trying to make use of pkg-config to get the correct libraries. The latest libuv is still broken in this regard, but we'll at least be in a position to use it. * Allow the use of Ninja or make. The former runs faster in many environments, and automatically makes use of parallel builds. This also allows for system installed dependencies--though not through the Makefile just yet--and adds support for FreeBSD. This also make us build libuv and luajit as static libraries only, since we're only concerned about having static libraries for our bundled dependencies.
2014-03-03 16:09:06 +01:00
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
add_subdirectory(src/nvim)
build: cmake: GetCompileFlags: include CMAKE_C_FLAGS (#10957) Calls `GetCompileFlags` from `src/nvim` directory, to include `--coverage` (and any others).
2019-09-06 20:36:05 +02:00
get_directory_property(NVIM_VERSION_CFLAGS DIRECTORY src/nvim DEFINITION NVIM_VERSION_CFLAGS)
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
add_subdirectory(test/includes)
version: Add compilation info.
2014-11-09 13:52:15 +01:00
add_subdirectory(config)
build: `oldtest` target: TEST_FILE, NVIM_PRG (#6098) - Add support for TEST_FILE to the `oldtest` target, for consistency with the busted/lua tests. Caveat: with the busted/lua tests TEST_FILE takes a full path, whereas for `oldtest` it must be "test_foo.res". - Add support for NVIM_PRG, again so that all test-related targets are consistent. - Use consistent name for NVIM_PRG. But still need to support NVIM_PROG for QuickBuild CI. Note: The `oldtest` target is driven by the top-level Makefile, because it requires a TTY. CMake 3.2 added a USES_TERMINAL flag to add_custom_target(). But we support CMake 2.8... add_custom_target(oldtest COMMAND make clean COMMAND make NVIM_PRG=$<TARGET_FILE:nvim> $ENV{MAKEOVERRIDES} DEPENDS nvim WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/testdir" USES_TERMINAL true )
2017-02-12 01:02:54 +01:00
add_subdirectory(test/functional/fixtures) # compile test programs
cmake: Generate tags and some vim syntax elements
2015-04-02 18:45:34 +02:00
add_subdirectory(runtime)
tests: use runtime from build for doc/tags with :help (#10479) This is better practice in general, and allows to remove the "helptags ALL" hacks. Ref: https://github.com/neovim/neovim/issues/8824 Ref: https://github.com/neovim/neovim/commit/f1b67c3453c * Makefile: fix dependencies with regard to helptags - use the file as the main target to avoid unnecessary triggering - use "make oldtest" on Travis to ensure it gets built
2019-08-28 22:47:54 +02:00
get_directory_property(GENERATED_HELP_TAGS DIRECTORY runtime DEFINITION GENERATED_HELP_TAGS)
win/package: move gui shim to its runtime folder (#8418) Close #7517 gui shim is for nvim-qt only.
2018-05-20 08:27:52 +02:00
if(WIN32)
install_helper(
FILES ${DEPS_PREFIX}/share/nvim-qt/runtime/plugin/nvim_gui_shim.vim
DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/nvim-qt/runtime/plugin)
endif()
job: Allow spawning jobs connected to pseudo terminals
2015-02-23 16:34:20 +01:00
build: install with the correct permissions The install() command will create the parent directories, but it does so with the user's umask. We want to do our best to make sure the correct permissions are being set, without clobbering existing permissions. To do this, this commit introduces an install_helper(), which is similar in signature to the install() command, to help ensure that directories are created ahead of the actual install() command. This will attempt to use 0644 permissions for files and 0755 permissions for directories by default--though they can be overridden. To make this work correctly, without trying to introduce some mechanism with setting the umask, it meant that there's a small portion that makes use of an "internal" version of the file() command. It has been tested on CMake 2.8.11, 2.8.12, and 3.0.2, and works correctly on all versions. This fixes #1201 and #1086.
2014-09-19 13:37:22 +02:00
# Setup some test-related bits. We do this after going down the tree because we
# need some of the targets.
Don't require busted. Only provide the unittest target if busted was found. And only build nvim-test if the unittest target exists by excluding nvim-test from all. Note: this means nvim-test won't be built by default, but it will be built when you try to run unittests.
2014-03-22 12:14:55 +01:00
if(BUSTED_PRG)
Generate a lua module to help pass build-related settings. This allows us to avoid hard-coding paths and using environment variables to communicate key information to unit tests, which fits with the overall goal of making sure that folks driving CMake directly can continue to do out-of-tree builds.
2014-04-30 11:10:37 +02:00
get_property(TEST_INCLUDE_DIRS DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
PROPERTY INCLUDE_DIRECTORIES)
Set the policy to 'OLD' to avoid warning CMP0026 in CMake 3.0.
2014-07-15 23:35:08 +02:00
Fix running tests from Ninja
2016-05-16 12:49:32 +02:00
# When running tests from 'ninja' we need to use the
# console pool: to do so we need to use the USES_TERMINAL
# option, but this is only available in CMake 3.2
set(TEST_TARGET_ARGS)
if(NOT (${CMAKE_VERSION} VERSION_LESS 3.2.0))
list(APPEND TEST_TARGET_ARGS "USES_TERMINAL")
endif()
build: create prereq targets for test dependencies This will help make sure that we build all the right prereqs before manually running tests under QuickBuild. Notice that shell-test has been added as a prereq for the functional tests, since it's a requirement for testing the terminal features.
2015-05-08 12:07:56 +02:00
set(UNITTEST_PREREQS nvim-test unittest-headers)
tests: fix system_spec when run with clipboard manager (#10956) * tests: move os_kill to functional helpers * tests: fix system_spec when run with clipboard manager Replaces "xclip" with a dedicated helper program. Fixes: https://github.com/neovim/neovim/issues/4900#issuecomment-501866842
2019-09-12 03:26:35 +02:00
set(FUNCTIONALTEST_PREREQS nvim printargs-test shell-test streams-test ${GENERATED_HELP_TAGS})
test: system([...])
2016-08-25 18:28:54 +02:00
if(NOT WIN32)
list(APPEND FUNCTIONALTEST_PREREQS tty-test)
Windows: Fix functionaltest fixtures
2015-12-21 00:11:23 +01:00
endif()
build: create prereq targets for test dependencies This will help make sure that we build all the right prereqs before manually running tests under QuickBuild. Notice that shell-test has been added as a prereq for the functional tests, since it's a requirement for testing the terminal features.
2015-05-08 12:07:56 +02:00
set(BENCHMARK_PREREQS nvim tty-test)
# Useful for automated build systems, if they want to manually run the tests.
add_custom_target(unittest-prereqs
DEPENDS ${UNITTEST_PREREQS})
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_target_properties(unittest-prereqs PROPERTIES FOLDER test)
build: create prereq targets for test dependencies This will help make sure that we build all the right prereqs before manually running tests under QuickBuild. Notice that shell-test has been added as a prereq for the functional tests, since it's a requirement for testing the terminal features.
2015-05-08 12:07:56 +02:00
add_custom_target(functionaltest-prereqs
DEPENDS ${FUNCTIONALTEST_PREREQS})
add_custom_target(benchmark-prereqs
DEPENDS ${BENCHMARK_PREREQS})
cmake: Allow building without Luajit By default Neovim searched a Luajit instalation and linked against the luajit library. In practice Neovim only requires luajit to run the unit tests. All other targets only require lua and the correct lua modules. This commit: 1. Remove the strict dependency on Luajit 2. Makes the unittest target depend on the lua 'ffi' module. If the module is not available the target is not enabled and a message is displayed.
2016-05-08 04:06:46 +02:00
check_lua_module(${LUA_PRG} "ffi" LUA_HAS_FFI)
if(LUA_HAS_FFI)
add_custom_target(unittest
COMMAND ${CMAKE_COMMAND}
-DBUSTED_PRG=${BUSTED_PRG}
-DLUA_PRG=${LUA_PRG}
-DWORKING_DIR=${CMAKE_CURRENT_SOURCE_DIR}
-DBUSTED_OUTPUT_TYPE=${BUSTED_OUTPUT_TYPE}
-DTEST_DIR=${CMAKE_CURRENT_SOURCE_DIR}/test
-DBUILD_DIR=${CMAKE_BINARY_DIR}
-DTEST_TYPE=unit
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
DEPENDS ${UNITTEST_PREREQS}
${TEST_TARGET_ARGS})
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_target_properties(unittest PROPERTIES FOLDER test)
cmake: Allow building without Luajit By default Neovim searched a Luajit instalation and linked against the luajit library. In practice Neovim only requires luajit to run the unit tests. All other targets only require lua and the correct lua modules. This commit: 1. Remove the strict dependency on Luajit 2. Makes the unittest target depend on the lua 'ffi' module. If the module is not available the target is not enabled and a message is displayed.
2016-05-08 04:06:46 +02:00
else()
build: `oldtest` target: TEST_FILE, NVIM_PRG (#6098) - Add support for TEST_FILE to the `oldtest` target, for consistency with the busted/lua tests. Caveat: with the busted/lua tests TEST_FILE takes a full path, whereas for `oldtest` it must be "test_foo.res". - Add support for NVIM_PRG, again so that all test-related targets are consistent. - Use consistent name for NVIM_PRG. But still need to support NVIM_PROG for QuickBuild CI. Note: The `oldtest` target is driven by the top-level Makefile, because it requires a TTY. CMake 3.2 added a USES_TERMINAL flag to add_custom_target(). But we support CMake 2.8... add_custom_target(oldtest COMMAND make clean COMMAND make NVIM_PRG=$<TARGET_FILE:nvim> $ENV{MAKEOVERRIDES} DEPENDS nvim WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/testdir" USES_TERMINAL true )
2017-02-12 01:02:54 +01:00
message(WARNING "disabling unit tests: no Luajit FFI in ${LUA_PRG}")
cmake: Allow building without Luajit By default Neovim searched a Luajit instalation and linked against the luajit library. In practice Neovim only requires luajit to run the unit tests. All other targets only require lua and the correct lua modules. This commit: 1. Remove the strict dependency on Luajit 2. Makes the unittest target depend on the lua 'ffi' module. If the module is not available the target is not enabled and a message is displayed.
2016-05-08 04:06:46 +02:00
endif()
test: Replace vroom by lua/busted for functional tests The 'lupa' python package provides a simple way to seamless integrate lua and python code. This commit replaces vroom by a python script that exposes the 'neovim' package to a lua state, and invokes busted to run functional tests. This is a temporary solution that will enable writing functional tests using lua/bused while a lua client library is not available. The reason for dropping vroom is flexibility: Lua/busted has a nice DSL-style syntax while also providing the customization power of a full programming language. Another reason is to use a single framework for unit/functional tests. Two other changes were performed in this commit: - Instead of "gcc-unittest/gcc-ia32", the travis builds for gcc are now identified by "gcc/gcc-32". They will run unit/functional tests for both 64 and 32 bits. - Old integration tests(in src/nvim/testdir) are now ran by the 'oldtest' target
2014-09-29 14:43:52 +02:00
Raise minimum CMake version to 2.8.12 and remove compat code 2.8.12 is supported by our main CI targets and [repology] confirms that this is broadly supported. [repology]: https://repology.org/metapackage/cmake/information
2018-06-16 16:20:25 +02:00
if(LUA_HAS_FFI)
set(TEST_LIBNVIM_PATH $<TARGET_FILE:nvim-test>)
cmake: Set TEST_LIBNVIM_PATH to empty string when not unit testing
2018-02-01 19:12:49 +01:00
else()
Raise minimum CMake version to 2.8.12 and remove compat code 2.8.12 is supported by our main CI targets and [repology] confirms that this is broadly supported. [repology]: https://repology.org/metapackage/cmake/information
2018-06-16 16:20:25 +02:00
set(TEST_LIBNVIM_PATH "")
cmake: Set TEST_LIBNVIM_PATH to empty string when not unit testing
2018-02-01 19:12:49 +01:00
endif()
Raise minimum CMake version to 2.8.12 and remove compat code 2.8.12 is supported by our main CI targets and [repology] confirms that this is broadly supported. [repology]: https://repology.org/metapackage/cmake/information
2018-06-16 16:20:25 +02:00
configure_file(
${CMAKE_SOURCE_DIR}/test/config/paths.lua.in
${CMAKE_BINARY_DIR}/test/config/paths.lua.gen)
file(GENERATE
OUTPUT ${CMAKE_BINARY_DIR}/test/config/paths.lua
INPUT ${CMAKE_BINARY_DIR}/test/config/paths.lua.gen)
cmake: Set TEST_LIBNVIM_PATH to empty string when not unit testing
2018-02-01 19:12:49 +01:00
CMake: Rename target "test" to "functionaltest". Remove build warning: The target name "test" is reserved or not valid for certain CMake features, such as generator expressions, and may result in undefined behavior.
2014-11-05 11:54:20 +01:00
add_custom_target(functionaltest
test: Replace vroom by lua/busted for functional tests The 'lupa' python package provides a simple way to seamless integrate lua and python code. This commit replaces vroom by a python script that exposes the 'neovim' package to a lua state, and invokes busted to run functional tests. This is a temporary solution that will enable writing functional tests using lua/bused while a lua client library is not available. The reason for dropping vroom is flexibility: Lua/busted has a nice DSL-style syntax while also providing the customization power of a full programming language. Another reason is to use a single framework for unit/functional tests. Two other changes were performed in this commit: - Instead of "gcc-unittest/gcc-ia32", the travis builds for gcc are now identified by "gcc/gcc-32". They will run unit/functional tests for both 64 and 32 bits. - Old integration tests(in src/nvim/testdir) are now ran by the 'oldtest' target
2014-09-29 14:43:52 +02:00
COMMAND ${CMAKE_COMMAND}
test: Remove run-functional-tests.py Now that the lua client is available, python/lupa are no longer necessary to run the functional tests. The helper functions previously defined in run-functional-tests.py were adapted to test/functional/helpers.lua.
2014-10-08 17:56:28 +02:00
-DBUSTED_PRG=${BUSTED_PRG}
Pass busted the path to the detected Lua interpreter Otherwise, busted may run a different interpreter than the one we detected, without the capabilities we expect. (For instance, we might have detected the luajit interpreter, but busted might run the lua interpreter, without the ffi module.)
2016-07-13 09:37:50 +02:00
-DLUA_PRG=${LUA_PRG}
build: fix running of functional tests directly with CMake If you aren't just building everything into build/, then the functional tests fail because they can't find the nvim executable. Let's pass in the location of the nvim executable, and set NVIM_PRG environment variable accordingly.
2014-11-05 13:26:35 +01:00
-DNVIM_PRG=$<TARGET_FILE:nvim>
test: Replace vroom by lua/busted for functional tests The 'lupa' python package provides a simple way to seamless integrate lua and python code. This commit replaces vroom by a python script that exposes the 'neovim' package to a lua state, and invokes busted to run functional tests. This is a temporary solution that will enable writing functional tests using lua/bused while a lua client library is not available. The reason for dropping vroom is flexibility: Lua/busted has a nice DSL-style syntax while also providing the customization power of a full programming language. Another reason is to use a single framework for unit/functional tests. Two other changes were performed in this commit: - Instead of "gcc-unittest/gcc-ia32", the travis builds for gcc are now identified by "gcc/gcc-32". They will run unit/functional tests for both 64 and 32 bits. - Old integration tests(in src/nvim/testdir) are now ran by the 'oldtest' target
2014-09-29 14:43:52 +02:00
-DWORKING_DIR=${CMAKE_CURRENT_SOURCE_DIR}
-DBUSTED_OUTPUT_TYPE=${BUSTED_OUTPUT_TYPE}
-DTEST_DIR=${CMAKE_CURRENT_SOURCE_DIR}/test
-DBUILD_DIR=${CMAKE_BINARY_DIR}
-DTEST_TYPE=functional
build: fix CMAKE_MODULE_PATH usage Fixes #1447. `CMAKE_MODULE_PATH` is meant to be a list of directories, and as such, is not the proper way to launch our scripts. Let's use `${PROJECT_SOURCE_DIR}/cmake` instead. Also, let's not outright set `CMAKE_MODULE_PATH`, but instead append our location to the list.
2014-11-11 01:26:01 +01:00
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 12:49:32 +02:00
DEPENDS ${FUNCTIONALTEST_PREREQS}
${TEST_TARGET_ARGS})
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_target_properties(functionaltest functionaltest-prereqs
PROPERTIES FOLDER test)
vim-patch:7.4.497 #2295 Problem: With some regexp patterns the NFA engine uses many states and becomes very slow. To the user it looks like Vim freezes. Solution: When the number of states reaches a limit fall back to the old engine. (Christian Brabandt) https://github.com/vim/vim/releases/tag/v7-4-497 Helped-by: David Bürgin <676c7473@gmail.com> Helped-by: Justin M. Keyes <justinkz@gmail.com> Helped-by: Scott Prager <splinterofchaos@gmail.com>
2015-03-28 22:28:37 +01:00
add_custom_target(benchmark
COMMAND ${CMAKE_COMMAND}
-DBUSTED_PRG=${BUSTED_PRG}
Pass busted the path to the detected Lua interpreter Otherwise, busted may run a different interpreter than the one we detected, without the capabilities we expect. (For instance, we might have detected the luajit interpreter, but busted might run the lua interpreter, without the ffi module.)
2016-07-13 09:37:50 +02:00
-DLUA_PRG=${LUA_PRG}
vim-patch:7.4.497 #2295 Problem: With some regexp patterns the NFA engine uses many states and becomes very slow. To the user it looks like Vim freezes. Solution: When the number of states reaches a limit fall back to the old engine. (Christian Brabandt) https://github.com/vim/vim/releases/tag/v7-4-497 Helped-by: David Bürgin <676c7473@gmail.com> Helped-by: Justin M. Keyes <justinkz@gmail.com> Helped-by: Scott Prager <splinterofchaos@gmail.com>
2015-03-28 22:28:37 +01:00
-DNVIM_PRG=$<TARGET_FILE:nvim>
-DWORKING_DIR=${CMAKE_CURRENT_SOURCE_DIR}
-DBUSTED_OUTPUT_TYPE=${BUSTED_OUTPUT_TYPE}
-DTEST_DIR=${CMAKE_CURRENT_SOURCE_DIR}/test
-DBUILD_DIR=${CMAKE_BINARY_DIR}
-DTEST_TYPE=benchmark
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 12:49:32 +02:00
DEPENDS ${BENCHMARK_PREREQS}
${TEST_TARGET_ARGS})
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_target_properties(benchmark benchmark-prereqs PROPERTIES FOLDER test)
Don't require busted. Only provide the unittest target if busted was found. And only build nvim-test if the unittest target exists by excluding nvim-test from all. Note: this means nvim-test won't be built by default, but it will be built when you try to run unittests.
2014-03-22 12:14:55 +01:00
endif()
Tests: add luacheck for linting tests Source: https://github.com/mpeterv/luacheck Docs: http://luacheck.readthedocs.org/en/0.12.0/index.html Run via "make testlint".
2015-11-17 13:16:33 +01:00
Add Lua 5.1 as a third party dep Also add a functionaltest-lua target to run the functional tests using the lua interpreter and corresponding helper to top-level Makefile
2016-03-07 04:42:49 +01:00
if(BUSTED_LUA_PRG)
add_custom_target(functionaltest-lua
COMMAND ${CMAKE_COMMAND}
-DBUSTED_PRG=${BUSTED_LUA_PRG}
Pass busted the path to the detected Lua interpreter Otherwise, busted may run a different interpreter than the one we detected, without the capabilities we expect. (For instance, we might have detected the luajit interpreter, but busted might run the lua interpreter, without the ffi module.)
2016-07-13 09:37:50 +02:00
-DLUA_PRG=${LUA_PRG}
Add Lua 5.1 as a third party dep Also add a functionaltest-lua target to run the functional tests using the lua interpreter and corresponding helper to top-level Makefile
2016-03-07 04:42:49 +01:00
-DNVIM_PRG=$<TARGET_FILE:nvim>
-DWORKING_DIR=${CMAKE_CURRENT_SOURCE_DIR}
-DBUSTED_OUTPUT_TYPE=${BUSTED_OUTPUT_TYPE}
-DTEST_DIR=${CMAKE_CURRENT_SOURCE_DIR}/test
-DBUILD_DIR=${CMAKE_BINARY_DIR}
-DTEST_TYPE=functional
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 12:49:32 +02:00
DEPENDS ${FUNCTIONALTEST_PREREQS}
${TEST_TARGET_ARGS})
cmake: Organize targets into folders Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
2018-06-17 14:54:39 +02:00
set_target_properties(functionaltest-lua PROPERTIES FOLDER test)
Add Lua 5.1 as a third party dep Also add a functionaltest-lua target to run the functional tests using the lua interpreter and corresponding helper to top-level Makefile
2016-03-07 04:42:49 +01:00
endif()
Tests: add luacheck for linting tests Source: https://github.com/mpeterv/luacheck Docs: http://luacheck.readthedocs.org/en/0.12.0/index.html Run via "make testlint".
2015-11-17 13:16:33 +01:00
if(LUACHECK_PRG)
Improve luacheck setup [skip appveyor] - Move .luacheckrc to root, add read_globals=vim - Simplify lualint target, run it on all lua files - Lint preload.lua, but ignore W211 - Remove testlint target, included in lualint (and lint) - Clean up .luacheckrc
2019-07-04 05:30:16 +02:00
add_custom_target(lualint
COMMAND ${LUACHECK_PRG} -q runtime/ src/ test/
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR})
else()
add_custom_target(lualint false
COMMENT "lualint: LUACHECK_PRG not defined")
Tests: add luacheck for linting tests Source: https://github.com/mpeterv/luacheck Docs: http://luacheck.readthedocs.org/en/0.12.0/index.html Run via "make testlint".
2015-11-17 13:16:33 +01:00
endif()
CMake: Add CPack settings to CMakeLists.txt
2016-01-09 01:14:26 +01:00
set(CPACK_PACKAGE_NAME "Neovim")
set(CPACK_PACKAGE_VENDOR "neovim.io")
set(CPACK_PACKAGE_VERSION ${NVIM_VERSION_MEDIUM})
set(CPACK_PACKAGE_INSTALL_DIRECTORY "Neovim")
# Set toplevel directory/installer name as Neovim
set(CPACK_PACKAGE_FILE_NAME "Neovim")
set(CPACK_TOPLEVEL_TAG "Neovim")
set(CPACK_RESOURCE_FILE_LICENSE "${PROJECT_SOURCE_DIR}/LICENSE")
set(CPACK_NSIS_MODIFY_PATH ON)
set(CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL ON)
include(CPack)