kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-23 20:55:18 -07:00
Code Issues Packages Projects Releases Wiki Activity
9a1c61456b
neovim/CMakeLists.txt

729 lines
25 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 11:30:23 -07:00
# CMAKE REFERENCE
# intro: https://codingnest.com/basic-cmake/
# best practices (3.0+): https://gist.github.com/mbinna/c61dbb39bca0e4fb7d1f73b0d66a4fd1
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 07:20:25 -07: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 05:33:07 -07: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 06:39:15 -07:00
build: Specify old behavior for POLICY CMP0059. This is needed as long as we support cmake older than 2.8.12. When we bump the minimum version to 2.8.12, we can use target_compile_options() and add_compile_options() instead. Closes #4389
2016-03-09 08:25:28 -07:00
if(POLICY CMP0059)
cmake: Update comment on why CMP0059 is still set to OLD
2018-12-01 15:55:29 -07:00
# Needed for use of DEFINITIONS variable, which is used to collect the
# compilation flags for reporting in "nvim --version"
# https://github.com/neovim/neovim/pull/8558#issuecomment-398033140
cmake_policy(SET CMP0059 OLD)
build: Specify old behavior for POLICY CMP0059. This is needed as long as we support cmake older than 2.8.12. When we bump the minimum version to 2.8.12, we can use target_compile_options() and add_compile_options() instead. Closes #4389
2016-03-09 08:25:28 -07:00
endif()
add custom CMake module path
2014-02-24 13:54:45 -07: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-10 17:26:01 -07:00
list(APPEND CMAKE_MODULE_PATH "${PROJECT_SOURCE_DIR}/cmake")
add custom CMake module path
2014-02-24 13:54:45 -07:00
build: prevent in-tree builds for the time being, as it's not supported
2016-10-11 15:35:02 -07: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 05:54:39 -07: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 08:09:06 -07: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 05:15:42 -07: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 11:17:24 -07: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 05:15:42 -07: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 11:17:24 -07: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 07:57:12 -07: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 05:15:42 -07: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 07:57:12 -07:00
Fix CMakeLists.txt search paths for cross compile
2015-04-18 16:20:26 -07: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 08:09:06 -07:00
cmake: Enable -fdiagnostics-color=auto gcc flag. #3137
2015-08-27 00:56:46 -07: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 14:16:39 -07: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 08:32:41 -07:00
endif()
CMakeLists: enable USE_FNAME_CASE on Mac
2015-03-26 20:30:45 -07:00
win: Define USE_FNAME_CASE (#5962)
2017-01-17 08:32:41 -07: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-26 20:30:45 -07: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 14:16:39 -07: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 11:17:24 -07:00
option(ENABLE_LIBINTL "enable libintl" ON)
build/msvc: Add libiconv to bundled dependencies
2018-06-06 18:39:17 -07:00
option(ENABLE_LIBICONV "enable libiconv" ON)
build: Enable LTO (Link Time Optimization) #8654
2018-07-22 18:22:14 -07: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 11:17:24 -07:00
version: Add compilation info.
2014-11-09 05:52:15 -07:00
# Set default build type.
if(NOT CMAKE_BUILD_TYPE)
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07:00
message(STATUS "CMAKE_BUILD_TYPE not given, defaulting to 'Debug'")
set(CMAKE_BUILD_TYPE "Debug" CACHE STRING "Choose the type of build" FORCE)
version: Add compilation info.
2014-11-09 05:52:15 -07: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-19 20:58:47 -07:00
# Set available build types for CMake GUIs.
# A different build type can still be set by -DCMAKE_BUILD_TYPE=...
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 00:29:40 -07: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-19 20:58:47 -07: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 10:29:02 -07: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 06:20:00 -07: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-04 15:32:47 -07:00
set(NVIM_VERSION_MAJOR 0)
version bump
2018-12-30 16:44:49 -07:00
set(NVIM_VERSION_MINOR 4)
set(NVIM_VERSION_PATCH 0)
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 03:17:19 -07: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 06:20:00 -07:00
# API level
cmake: bump API version
2018-06-28 23:05:34 -07:00
set(NVIM_API_LEVEL 5) # 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 06:20:00 -07:00
set(NVIM_API_LEVEL_COMPAT 0) # Adjust this after a _breaking_ API change.
NVIM v0.3.2 Besides the "visible" improvements, this release features numerous internal improvements to the UI/screen code and test infrastructure. Numerous patches were merged from Vim, which are not mentioned below. FEATURES: 07ad5d71ab97 clipboard: Support custom VimL functions #9304 725da1feeb9a #9401 win/TUI: Improve terminal/console support 7a8dadbedb0b #9077 startup: Use $XDG_CONFIG_DIRS/nvim/sysinit.vim if it exists feec926633e3 #9299 support <cmd> mapping in more places 0653ed63a508 #9028 diff/highlight: Show underline for low-priority CursorLine bddcbbb5716a signs: Add "numhl" argument #9113 05f9c7c2f7f5 clipboard: support Wayland (#9230) 14ae394532aa #9052 TUI: add support for undercurl and underline color 4fa3492a6fcb #9023 man.vim: soft (dynamic) wrap #9023 API: 8b39e4ec7933 #6920 API: implement object namespaces b1aaa0a881ef API: Implement nvim_win_set_buf() #9100 8de87c7b1ca0 #8180 API: virtual text annotations (nvim_buf_set_virtual_text) 2b9fc9a13f14 #8660 API: add nvim_buf_is_loaded() API: buf_get_lines, buf_line_count handle unloaded buffers 88f77c28e52a API: nvim_buf_get_offset_for_line 94841e5eaebc API/UI: #8221 ext_newgrid, ext_hlstate (use line-based rather than char-based updates) UI b5cfac089409 #8806 TUI: use BCE again more often, (smoother resizes/scrolling) 77b5e9ae25fc #9315 screen: add missing status redraw when redraw_later(CLEAR) was used 5f15788dc3ac TUI: clip invalid regions on resize (#8779), fixes #8774 c936ae0f3688 #9193 TUI: improvements for scrolling and clearing f20427451e7f #9143 UI: disable clearing almost everywhere f4b2b6666189 #9079 TUI: always use safe cursor movement after resize d36afafc8dc7 #9211 ui_options: also send when starting or from OptionSet 67f80d485cec TUI: Avoid reset_cursor_color in old VTE #9191 e55ebae37340 #9021 don't erase screen on `:hi Normal` during startup c5790d91897c #8915 TUI: Hint wrapped lines to terminals. FIXES: 231de7253982 RPC: turn errors from async calls into notifications 907ad921bc2f TUI: Restore terminal title via "title stacking" (#9407) cb76a8a95f3a genappimage: Unset $ARGV0 at invocation #9376 b48efd9ba7bf #9347 TUI: FreeBSD: Improve support for BSD vt console c16529afa5c8 TUI: Konsole 18.07.70 supports DECSCUSR (#9364) aec096fc5b8a os/lang: use the correct LC_NUMERIC also for OS X 5fee0be91552 provider: improve error message (#9344) 3c42d7a10a04 TUI: alacritty supports set_cursor_color #9353 7bff9a5de842 TUI: Alacritty supports DECSCUSR (#9048) 57acfceabeb3 macOS: infer primary language if $LANG is empty #9345 bc132ae123d4 runtime/syntax: Fix highlighting of augroup contents (#9328) 715fdfee1ed5 #9297 VimL/confirm(): Show dialog even if :silent 799d9c32157c clipboard: Prefer xclip (#9302) 6dae7776ed0d provider/nodejs: fix npm,yarn detection 16bc1e9c1782 #9218 channel: avoid buffering output when only terminal and no callbacks are active 72fecad1ffe3 #8804 Fix crash in lang_init() on macOS if lang_region = NULL d58139877990 ruby: detect rbenv shims for other versions (#8733) e568ac7a68d3 #9123 third-party/unibilium: Fix parsing of extended capability entries c4c74c3883aa jobstart(): Fix hang on non-executable cwd #9204 1cf50cbfd9b7 provider/nodejs: Simultaneously query npm and yarn #9054 6c496db4b75e undo: Fix infinite loop if undo_read_byte returns EOF #2880 f8f83579ff42 #9034 'swapfile: always show dialog' CHANGES: c236e80cf3df #9024 --embed: wait for UI unless --headless 180b50dddc26 #9248 python: 'neovim' module was renamed to 'pynvim' 2000b6a64a9c #8589 VimL: Remove legacy aliases "v:errmsg", "v:shell_error", "v:this_session" deb18a050ef5 defaults: background=dark #2894 (#9205) c1187d4af013 defaults: win: 'shellpipe' for cmd.exe (#8827)
2018-12-30 15:58:46 -07: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 10:46:37 -07:00
CMake: Force use of project directory to look for Git data. Before this change, building Neovim would recursively search parent directories for a .git directory. If Neovim was downloaded as a tarball (i.e. without a .git directory), but placed in a subdirectory of a Git repository, this caused a CMake error. Such a situation could occur when packaging Neovim, for example. Unfortunately, the previous attempt in #3317 did not fix this problem.
2015-09-29 12:22:55 -07:00
file(TO_CMAKE_PATH ${CMAKE_CURRENT_LIST_DIR}/.git FORCED_GIT_DIR)
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 03:17:19 -07:00
include(GetGitRevisionDescription)
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 10:29:02 -07:00
get_git_head_revision(GIT_REFSPEC NVIM_VERSION_COMMIT)
if(NVIM_VERSION_COMMIT) # is a git repo
git_describe(NVIM_VERSION_MEDIUM)
# `git describe` annotates the most recent tagged release; for pre-release
# builds we must replace that with the unreleased version.
string(REGEX REPLACE "^v[0-9]+\\.[0-9]+\\.[0-9]+"
"v${NVIM_VERSION_MAJOR}.${NVIM_VERSION_MINOR}.${NVIM_VERSION_PATCH}"
NVIM_VERSION_MEDIUM
${NVIM_VERSION_MEDIUM})
endif()
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 03:17:19 -07:00
version: Add compilation info.
2014-11-09 05:52:15 -07: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 06:39:15 -07:00
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
build: default to using -O2 for release builds The -O3 optimization level can often lead to dangerous (and sometimes incorrect) optimizations being performed. So let's use a level that's more stable.
2014-11-07 04:21:54 -07:00
# Default to -O2 on release builds.
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 11:38:34 -07:00
if(CMAKE_C_FLAGS_RELEASE MATCHES "-O3")
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07:00
message(STATUS "Replacing -O3 in CMAKE_C_FLAGS_RELEASE with -O2")
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 11:38:34 -07:00
string(REPLACE "-O3" "-O2" CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
endif()
build: default to using -O2 for release builds The -O3 optimization level can often lead to dangerous (and sometimes incorrect) optimizations being performed. So let's use a level that's more stable.
2014-11-07 04:21:54 -07:00
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-29 17:03:08 -07: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 03:15:55 -07: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-29 17:03:08 -07: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 03:15:55 -07: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-29 17:03:08 -07: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 03:15:55 -07:00
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 00:29:40 -07: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 03:14:38 -07: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-20 17:30:21 -07: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 00:29:40 -07: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-20 17:30:21 -07: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 00:29:40 -07: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 03:14:38 -07:00
endif()
CMake: Set -Wconversion by default.
2014-11-18 06:01:24 -07:00
# Enable -Wconversion.
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-27 19:00:09 -07:00
if(NOT MSVC)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wconversion")
endif()
CMake: Set -Wconversion by default.
2014-11-18 06:01:24 -07:00
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-11 17:02:54 -07: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 15:06:18 -07: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-11 17:02:54 -07: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 01:42:59 -07: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 04:02:42 -07: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 14:22:30 -07: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 01:42:59 -07: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 14:22:30 -07: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 01:42:59 -07: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 02:08:26 -07: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 01:42:59 -07: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 02:08:26 -07:00
if(NOT HAS_ACCEPTABLE_FORTIFY)
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07: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 10:45:21 -07: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-26 15:00:33 -07:00
if(NOT _FORTIFY_SOURCE_PREFIX STREQUAL "")
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07: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 10:45:21 -07:00
endif()
build: turn down the _FORTIFY_SOURCE level on gcc >= 4.0
2014-11-04 15:06:18 -07: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 10:45:21 -07: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 15:06:18 -07: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 11:38:34 -07: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 09:45:34 -07: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 11:38:34 -07: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 14:02:41 -07:00
check_c_source_compiles("
#include <execinfo.h>
int main(void)
{
void *trace[1];
int trace_size = backtrace(trace, 1);
return 0;
}
" HAVE_EXECINFO_BACKTRACE)
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-27 19:00:09 -07:00
if(MSVC)
# XXX: /W4 gives too many warnings. #3241
add_definitions(/W3 -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-04 16:44:23 -07: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-27 19:00:09 -07:00
else()
add_definitions(-Wall -Wextra -pedantic -Wno-unused-parameter
build: Check if compiler supports -Wvla before use OpenBSD's GCC (4.2.1) doesn't have the -Wvla flag.
2015-10-02 09:51:45 -07:00
-Wstrict-prototypes -std=gnu99)
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-27 18:20:27 -07:00
Detect support for and use -Wimplicit-fallthrough
2017-05-02 20:58:04 -07:00
check_c_compiler_flag(-Wimplicit-fallthrough HAS_WIMPLICIT_FALLTHROUGH_FLAG)
if(HAS_WIMPLICIT_FALLTHROUGH_FLAG)
add_definitions(-Wimplicit-fallthrough)
endif()
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-27 18:20:27 -07: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 04:44:02 -07:00
if(CMAKE_SYSTEM_NAME STREQUAL "FreeBSD" AND CMAKE_C_COMPILER_ID MATCHES "Clang")
ci: Disable -Wc11-extensions on FreeBSD Closes #4363.
2016-02-27 18:20:27 -07:00
add_definitions(-Wno-c11-extensions)
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-27 19:00:09 -07: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-26 15:00:33 -07: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 06:32:09 -07: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-04 16:44:23 -07: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 06:31:33 -07: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 06:32:09 -07: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-14 16:08:41 -07:00
build: Check if compiler supports -Wvla before use OpenBSD's GCC (4.2.1) doesn't have the -Wvla flag.
2015-10-02 09:51:45 -07:00
# OpenBSD's GCC (4.2.1) doesn't have -Wvla
check_c_compiler_flag(-Wvla HAS_WVLA_FLAG)
if(HAS_WVLA_FLAG)
add_definitions(-Wvla)
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-13 16:46:32 -07: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)
add_definitions(-fstack-protector-strong)
elseif(HAS_FSTACK_PROTECTOR_FLAG)
add_definitions(-fstack-protector --param ssp-buffer-size=4)
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-26 15:00:33 -07:00
endif()
cmake: Enable -fdiagnostics-color=auto gcc flag. #3137
2015-08-27 00:56:46 -07:00
check_c_compiler_flag(-fdiagnostics-color=auto HAS_DIAG_COLOR_FLAG)
if(HAS_DIAG_COLOR_FLAG)
add_definitions(-fdiagnostics-color=auto)
endif()
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 05:33:07 -07:00
if(CMAKE_C_COMPILER_ID STREQUAL "GNU")
build/gcc: disable -Warray-bounds entirely #7923 We need to disable -Warray-bounds locally for kbtree.h, but we can't because _Pragma("GCC diagnostic pop") is broken in GCC 5.x+. So this commit disables -Warray-bounds entirely (for GCC only). GCC bug: "_Pragma diagnostic 'ignored' in macro with strict-overflow not suppressing warning fully with -Werror" https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66099 ref https://github.com/neovim/neovim/pull/7083#issuecomment-326323599 closes #7921
2018-01-27 10:23:03 -07:00
# 1. Array-bounds testing is broken in some GCC versions before 4.8.5.
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56273
# 2. But _Pragma("...ignored") is broken (unresolved) in GCC 5+:
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66099
# So we must disable -Warray-bounds globally for GCC (for kbtree.h, #7083).
check_c_compiler_flag(-Wno-array-bounds HAS_NO_ARRAY_BOUNDS_FLAG)
if(HAS_NO_ARRAY_BOUNDS_FLAG)
add_definitions(-Wno-array-bounds)
build: disable array bounds checking in gcc < 4.8.5 Thanks to James McCoy (jamessan) for finding the source of this issue.
2017-07-27 03:48:00 -07:00
endif()
endif()
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07: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-14 16:08:41 -07:00
if(TRAVIS_CI_BUILD)
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07:00
message(STATUS "Travis/QuickBuild CI build enabled")
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-14 16:08:41 -07:00
add_definitions(-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 10:55:08 -07:00
if(DEFINED ENV{BUILD_32BIT})
# Get some test coverage for unsigned char
add_definitions(-funsigned-char)
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-14 16:08:41 -07: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 05:27:20 -07:00
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 06:39:15 -07:00
if(CMAKE_BUILD_TYPE MATCHES Debug)
set(DEBUG 1)
else()
set(DEBUG 0)
endif()
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-02 18:25:42 -07:00
option(LOG_LIST_ACTIONS "Add list actions logging" OFF)
CMake: Set custom RelWithDebInfo compile flags.
2014-11-08 04:49:04 -07: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 05:33:07 -07: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 07:18:55 -07: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-24 19:16:00 -07: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-13 22:43:07 -07:00
# For ptsname(). #6743
cmake: Linux: define _GNU_SOURCE. Closes #4042
2016-01-24 19:16:00 -07: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-14 18:14:28 -07:00
endif()
Add missing linker flags required for LuaJIT on 64-bit Mac OS X. This was brought up in #1294.
2014-10-17 03:50:13 -07: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 12:00:43 -07:00
include_directories("${PROJECT_BINARY_DIR}/config")
include_directories("${PROJECT_SOURCE_DIR}/src")
find_package(LibUV 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 04:21:13 -07: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 12:00:43 -07: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-04 20:21:51 -07: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 04:21:13 -07:00
include_directories(SYSTEM ${MSGPACK_INCLUDE_DIRS})
Add cmake module for finding msgpack
2014-04-10 11:39:34 -07: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 04:57:08 -07: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-20 16:33:09 -07: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 04:57:08 -07: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-05 17:48:49 -07: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 04:57:08 -07: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 11:17:24 -07: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 04:57:08 -07: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-20 16:33:09 -07: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 11:55:28 -07:00
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 08:05:48 -07: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)
Unset CMAKE_REQUIRED_* after they're done being used As of CMake 3.12, check_include_files() also link the check executable against the libraries listed in CMAKE_REQUIRED_LIBRARIES. Therefore we should unset the CMAKE_REQUIRED_* variables after each respective use to avoid them unnecessarily bleeding into other checks.
2018-12-01 13:28:33 -07:00
unset(CMAKE_REQUIRED_LIBRARIES)
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 08:05:48 -07:00
if(MSGPACK_HAS_FLOAT32)
cmake: Prefer add_definitions() for setting preprocessor defines
2018-06-17 20:29:39 -07:00
add_definitions(-DNVIM_MSGPACK_HAS_FLOAT32)
cmake: Detect whether msgpack-c has MSGPACK_OBJECT_FLOAT{32,64} types
2017-03-30 08:05:48 -07: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-17 17:06:47 -07: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 08:06:05 -07: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 14:16:39 -07:00
if(FEAT_TUI)
find_package(Unibilium REQUIRED)
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-16 20:13:35 -07: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)
Unset CMAKE_REQUIRED_* after they're done being used As of CMake 3.12, check_include_files() also link the check executable against the libraries listed in CMAKE_REQUIRED_LIBRARIES. Therefore we should unset the CMAKE_REQUIRED_* variables after each respective use to avoid them unnecessarily bleeding into other checks.
2018-12-01 13:28:33 -07:00
unset(CMAKE_REQUIRED_INCLUDES)
unset(CMAKE_REQUIRED_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-16 20:13:35 -07:00
if(UNIBI_HAS_VAR_FROM)
cmake: Prefer add_definitions() for setting preprocessor defines
2018-06-17 20:29:39 -07: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-16 20:13:35 -07:00
endif()
build: dependencies: specify minimum versions
2018-11-03 13:28:07 -07: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 14:16:39 -07: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 08:06:05 -07:00
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 06:41:53 -07:00
find_package(LibVterm REQUIRED)
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 01:14:19 -07:00
if(WIN32)
build: dependencies: specify minimum versions
2018-11-03 13:28:07 -07: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 01:14:19 -07:00
include_directories(SYSTEM ${WINPTY_INCLUDE_DIRS})
endif()
CMake: Add option for Clang TSan, rename option ASAN -> ASAN_UBSAN.
2015-06-09 01:43:22 -07:00
option(CLANG_ASAN_UBSAN "Enable Clang address & undefined behavior sanitizer for nvim binary." OFF)
CMake: Add option for Clang MSan.
2015-06-08 09:49:23 -07: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 01:43:22 -07: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 09:45:34 -07:00
message(FATAL_ERROR "Sanitizers cannot be enabled simultaneously")
CMake: Add option for Clang MSan.
2015-06-08 09:49:23 -07:00
endif()
CMake: Add option for Clang TSan, rename option ASAN -> ASAN_UBSAN.
2015-06-09 01:43:22 -07: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 09:45:34 -07: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 07:40:08 -07: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 11:17:24 -07:00
if(CMAKE_SYSTEM_NAME MATCHES "OpenBSD|FreeBSD|Windows") # see #5318
message(STATUS "skipping jemalloc on this system: ${CMAKE_SYSTEM_NAME}")
Disable use of jemalloc in OpenBSD Works around #3434, turning off the use of jemalloc in OpenBSD.
2016-09-10 04:12:09 -07:00
option(ENABLE_JEMALLOC "enable jemalloc" OFF)
else()
option(ENABLE_JEMALLOC "enable jemalloc" ON)
endif()
Make jemalloc optional
2015-10-26 11:33:50 -07:00
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 11:17:24 -07:00
if(ENABLE_JEMALLOC)
Make jemalloc optional
2015-10-26 11:33:50 -07:00
if(CLANG_ASAN_UBSAN OR CLANG_MSAN OR CLANG_TSAN)
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07:00
message(STATUS "Sanitizers enabled; disabling jemalloc")
Make jemalloc optional
2015-10-26 11:33:50 -07: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 11:17:24 -07:00
find_package(JeMalloc REQUIRED)
include_directories(SYSTEM ${JEMALLOC_INCLUDE_DIRS})
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 07:40:08 -07:00
endif()
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 11:17:24 -07: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 14:09:47 -07: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 12:00:43 -07: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 11:17:24 -07: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 14:18:04 -07: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 12:00:43 -07: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 11:52:12 -07:00
# Determine platform's threading library. Set CMAKE_THREAD_PREFER_PTHREAD
Remove pthread fatal check from CMakeLists.txt #891
2014-06-25 14:47:27 -07: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 11:52:12 -07: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-08 19:40:57 -07: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 08:09:06 -07:00
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
Allow building as a static -fPIC library
2014-11-30 19:22:46 -07: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-08 19:40:57 -07: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 08:30:50 -07: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 04:12:18 -07: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 04:12:10 -07: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 05:21:32 -07: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 04:12:18 -07:00
if(NOT LUA_PRG)
CMake: Search all possibly usable Lua executables. (#4858)
2016-06-03 09:21:29 -07:00
foreach(CURRENT_LUA_PRG luajit lua5.1 lua5.2 lua)
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 04:12:18 -07:00
# If LUA_PRG is set find_program() will not search
unset(LUA_PRG CACHE)
unset(LUA_PRG_WORKS)
find_program(LUA_PRG ${CURRENT_LUA_PRG})
if(LUA_PRG)
check_lua_deps(${LUA_PRG} "${LUA_DEPENDENCIES}" LUA_PRG_WORKS)
if(LUA_PRG_WORKS)
break()
endif()
endif()
endforeach()
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 03:06:35 -07: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 04:12:10 -07:00
if(NOT LUA_PRG_WORKS)
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07: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 03:06:35 -07:00
endif()
build: adjust some messages (#9087)
2018-10-06 09:45:34 -07: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 03:06:35 -07: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 04:37:22 -07: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 10:54:14 -07: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-06 20:42:49 -07: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 04:37:22 -07:00
if(NOT BUSTED_OUTPUT_TYPE)
build: Default BUSTED_OUTPUT_TYPE to "nvim" (#6811)
2017-05-25 05:51:53 -07: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 04:37:22 -07: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 08:09:06 -07: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 05:16:33 -07:00
find_program(LUACHECK_PRG luacheck)
eval: use gperf to generate the hash of builtin functions make api functions highlighted as builtins in vim.vim
2016-06-19 07:41:08 -07: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 04:37:22 -07: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 11:45:30 -07: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 11:12:51 -07: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 11:45:30 -07:00
install_helper(
FILES ${MANPAGES}
DESTINATION ${CMAKE_INSTALL_MANDIR}/man1)
cmake: Pass -DMIN_LOG_LEVEL as compiler definition - Check if MIN_LOG_LEVEL value is a number 0-3, default to INFO (1) or ignore it in Release mode - When TRAVIS_CI_BUILD is ON the default is DEBUG (0) - Add local.mk.example
2014-12-08 13:00:54 -07:00
# MIN_LOG_LEVEL for log.h
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-20 17:30:21 -07:00
if("${MIN_LOG_LEVEL}" MATCHES "^$")
message(STATUS "MIN_LOG_LEVEL not specified")
else()
cmake: Pass -DMIN_LOG_LEVEL as compiler definition - Check if MIN_LOG_LEVEL value is a number 0-3, default to INFO (1) or ignore it in Release mode - When TRAVIS_CI_BUILD is ON the default is DEBUG (0) - Add local.mk.example
2014-12-08 13:00:54 -07:00
if(NOT MIN_LOG_LEVEL MATCHES "^[0-3]$")
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-29 17:03:08 -07:00
message(FATAL_ERROR "invalid MIN_LOG_LEVEL: " ${MIN_LOG_LEVEL})
cmake: Pass -DMIN_LOG_LEVEL as compiler definition - Check if MIN_LOG_LEVEL value is a number 0-3, default to INFO (1) or ignore it in Release mode - When TRAVIS_CI_BUILD is ON the default is DEBUG (0) - Add local.mk.example
2014-12-08 13:00:54 -07:00
endif()
ci: MIN_LOG_LEVEL=2 (#6169) DEBUG_LOG_LEVEL is very noisy and causes a lot of disk activity. It is not needed on CI.
2017-02-24 03:03:56 -07:00
message(STATUS "MIN_LOG_LEVEL set to ${MIN_LOG_LEVEL}")
cmake: Pass -DMIN_LOG_LEVEL as compiler definition - Check if MIN_LOG_LEVEL value is a number 0-3, default to INFO (1) or ignore it in Release mode - When TRAVIS_CI_BUILD is ON the default is DEBUG (0) - Add local.mk.example
2014-12-08 13:00:54 -07:00
endif()
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 04:37:22 -07:00
# Go down the tree.
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 08:09:06 -07: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 04:37:22 -07:00
add_subdirectory(src/nvim)
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-20 17:30:21 -07:00
# Read compilation flags from src/nvim, used in config subdirectory below.
version: Add compilation info.
2014-11-09 05:52:15 -07:00
include(GetCompileFlags)
get_compile_flags(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 04:37:22 -07:00
add_subdirectory(test/includes)
version: Add compilation info.
2014-11-09 05:52:15 -07: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-11 17:02:54 -07:00
add_subdirectory(test/functional/fixtures) # compile test programs
cmake: Generate tags and some vim syntax elements
2015-04-02 09:45:34 -07:00
add_subdirectory(runtime)
win/package: move gui shim to its runtime folder (#8418) Close #7517 gui shim is for nvim-qt only.
2018-05-19 23:27:52 -07: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 08:34:20 -07: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 04:37:22 -07: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 04:14:55 -07: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 02:10:37 -07: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 14:35:08 -07:00
Fix running tests from Ninja
2016-05-16 03:49:32 -07: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 03:07:56 -07:00
set(UNITTEST_PREREQS nvim-test unittest-headers)
test: system([...])
2016-08-25 09:28:54 -07:00
set(FUNCTIONALTEST_PREREQS nvim printargs-test shell-test)
if(NOT WIN32)
list(APPEND FUNCTIONALTEST_PREREQS tty-test)
Windows: Fix functionaltest fixtures
2015-12-20 16:11:23 -07: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 03:07:56 -07: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 05:54:39 -07: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 03:07:56 -07: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-07 19:06:46 -07: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
functionaltest: Create lua helper for os.tmpname() In Windows Lua's os.tmpname() returns relative paths starting with \s, prepend them with $TEMP to generate a valid path. In OS X os.tmpname() returns paths in '/tmp' but they should be in '/private/tmp'. We cannot use os_name() for platform detection because some tests use tempname() before nvim is spawned, instead use one of the following: 1. Set SYSTEM_NAME environment variable before calling the tests, it is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows') 2. Call uname -s 3. Assume windows
2015-12-29 12:18:16 -07:00
-DSYSTEM_NAME=${CMAKE_SYSTEM_NAME}
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-07 19:06:46 -07:00
-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 05:54:39 -07: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-07 19:06:46 -07: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-11 17:02:54 -07: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-07 19:06:46 -07: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 05:43:52 -07: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 07:20:25 -07: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 11:12:49 -07: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 07:20:25 -07:00
set(TEST_LIBNVIM_PATH "")
cmake: Set TEST_LIBNVIM_PATH to empty string when not unit testing
2018-02-01 11:12:49 -07: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 07:20:25 -07: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 11:12:49 -07: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 03:54:20 -07: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 05:43:52 -07: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 08:56:28 -07: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 00:37:50 -07: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 05:26:35 -07: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 05:43:52 -07: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
functionaltest: Create lua helper for os.tmpname() In Windows Lua's os.tmpname() returns relative paths starting with \s, prepend them with $TEMP to generate a valid path. In OS X os.tmpname() returns paths in '/tmp' but they should be in '/private/tmp'. We cannot use os_name() for platform detection because some tests use tempname() before nvim is spawned, instead use one of the following: 1. Set SYSTEM_NAME environment variable before calling the tests, it is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows') 2. Call uname -s 3. Assume windows
2015-12-29 12:18:16 -07:00
-DSYSTEM_NAME=${CMAKE_SYSTEM_NAME}
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-10 17:26:01 -07:00
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 03:49:32 -07: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 05:54:39 -07: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 14:28:37 -07: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 00:37:50 -07: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 14:28:37 -07: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
functionaltest: Create lua helper for os.tmpname() In Windows Lua's os.tmpname() returns relative paths starting with \s, prepend them with $TEMP to generate a valid path. In OS X os.tmpname() returns paths in '/tmp' but they should be in '/private/tmp'. We cannot use os_name() for platform detection because some tests use tempname() before nvim is spawned, instead use one of the following: 1. Set SYSTEM_NAME environment variable before calling the tests, it is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows') 2. Call uname -s 3. Assume windows
2015-12-29 12:18:16 -07:00
-DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME}
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 14:28:37 -07:00
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 03:49:32 -07: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 05:54:39 -07: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 04:14:55 -07: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 05:16:33 -07: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-06 20:42:49 -07: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 00:37:50 -07: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-06 20:42:49 -07: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
functionaltest: Create lua helper for os.tmpname() In Windows Lua's os.tmpname() returns relative paths starting with \s, prepend them with $TEMP to generate a valid path. In OS X os.tmpname() returns paths in '/tmp' but they should be in '/private/tmp'. We cannot use os_name() for platform detection because some tests use tempname() before nvim is spawned, instead use one of the following: 1. Set SYSTEM_NAME environment variable before calling the tests, it is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows') 2. Call uname -s 3. Assume windows
2015-12-29 12:18:16 -07:00
-DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME}
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-06 20:42:49 -07:00
-P ${PROJECT_SOURCE_DIR}/cmake/RunTests.cmake
Fix running tests from Ninja
2016-05-16 03:49:32 -07: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 05:54:39 -07: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-06 20:42:49 -07: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 05:16:33 -07:00
if(LUACHECK_PRG)
add_custom_target(testlint
COMMAND ${CMAKE_COMMAND}
-DLUACHECK_PRG=${LUACHECK_PRG}
ci: Also lint lua code in src/nvim/lua
2017-05-25 06:50:06 -07:00
-DLUAFILES_DIR=${CMAKE_CURRENT_SOURCE_DIR}/test
-DIGNORE_PATTERN="*/preload.lua"
functionaltest: Create lua helper for os.tmpname() In Windows Lua's os.tmpname() returns relative paths starting with \s, prepend them with $TEMP to generate a valid path. In OS X os.tmpname() returns paths in '/tmp' but they should be in '/private/tmp'. We cannot use os_name() for platform detection because some tests use tempname() before nvim is spawned, instead use one of the following: 1. Set SYSTEM_NAME environment variable before calling the tests, it is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows') 2. Call uname -s 3. Assume windows
2015-12-29 12:18:16 -07:00
-DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME}
ci: Also lint lua code in src/nvim/lua
2017-05-25 06:50:06 -07:00
-P ${PROJECT_SOURCE_DIR}/cmake/RunLuacheck.cmake)
add_custom_target(
runtime/lua/vim/compat.lua ref #9280 Introduce the `vim.compat` module, to help environments with system Lua 5.2+ run the build/tests. Include the module implicitly in all tests. ref #8677 legacy `vim` module: beep buffer command dict eval firstline lastline line list open type window
2018-11-29 14:51:20 -07:00
lintbuiltinlua
ci: Also lint lua code in src/nvim/lua
2017-05-25 06:50:06 -07:00
COMMAND
${CMAKE_COMMAND}
-DLUACHECK_PRG=${LUACHECK_PRG}
-DLUAFILES_DIR=${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/lua
-DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME}
-DREAD_GLOBALS=vim
-P ${PROJECT_SOURCE_DIR}/cmake/RunLuacheck.cmake
)
runtime/lua/vim/compat.lua ref #9280 Introduce the `vim.compat` module, to help environments with system Lua 5.2+ run the build/tests. Include the module implicitly in all tests. ref #8677 legacy `vim` module: beep buffer command dict eval firstline lastline line list open type window
2018-11-29 14:51:20 -07:00
add_custom_target(
lintruntimelua
COMMAND
${CMAKE_COMMAND}
-DLUACHECK_PRG=${LUACHECK_PRG}
-DLUAFILES_DIR=${CMAKE_CURRENT_SOURCE_DIR}/runtime/lua
-DCMAKE_SYSTEM_NAME=${CMAKE_SYSTEM_NAME}
-DREAD_GLOBALS=vim
-P ${PROJECT_SOURCE_DIR}/cmake/RunLuacheck.cmake
)
ci: Also lint lua code in src/nvim/lua
2017-05-25 06:50:06 -07:00
# TODO(ZyX-I): Run linter for all lua code in src
add_custom_target(
lualint
runtime/lua/vim/compat.lua ref #9280 Introduce the `vim.compat` module, to help environments with system Lua 5.2+ run the build/tests. Include the module implicitly in all tests. ref #8677 legacy `vim` module: beep buffer command dict eval firstline lastline line list open type window
2018-11-29 14:51:20 -07:00
DEPENDS lintruntimelua
DEPENDS lintbuiltinlua
ci: Also lint lua code in src/nvim/lua
2017-05-25 06:50:06 -07: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 05:16:33 -07:00
endif()
CMake: Add CPack settings to CMakeLists.txt
2016-01-08 17:14:26 -07: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)
Reference in New Issue Copy Permalink