aboutsummaryrefslogtreecommitdiff
path: root/cmake/FindLibUV.cmake
Commit message (Collapse)AuthorAge
* build: cmake cleanup (#22251)dundargoc2023-03-02
| | | | | | | | - Remove unused code - Use consistent casing. Variable names such as LibLuV_LIBRARIES is needlessly jarring, even if the name might be technically correct. - Use title casing for packages. find_package(unibilium) requires the find_module to be named "Findunibilium.cmake", which makes it harder to spot when scanning the files. Instead, use "Unibilium".
* build: remove libfindmacros library (#22423)dundargoc2023-03-02
| | | | | | Large parts the library weren't being used, and the parts that were was overly abstracted for our use case. Additionally, part of its use case was to abstract pkgconfig boilerplate, which is no longer needed as pkgconfig has been removed in favor of relying on cmake alone in 09118052cee5aef978d6075db5287c1b6c27381a.
* build: remove pkgconfig-related code (#22422)dundargoc2023-02-26
| | | Cmake should already be able to find everything on its own.
* build: use libuv config file (#22209)ii142023-02-16
| | | | | | | | | Libuv's recent changes in their pc file breaks cmake; they are using -l:libuv.a for the linker, and it seems cmake can't resolve that. Prefer using their cmake config file instead instead, and use the find module as a fall-back in case it fails. Closes https://github.com/neovim/neovim/issues/22271.
* build(deps): bump libuv to HEAD - 62c2374a8 (#22166)Christian Clason2023-02-08
|
* build libuv cmake (#19632)Lewis Russell2022-08-12
| | | Co-authored-by: Daniel Hahler <git@thequod.de>
* fix(build): call find_package(Threads) before using its variablesJames McCoy2021-09-21
|
* build: add ${CMAKE_THREAD_LIBS_INIT} to LIBUV_LIBRARIESJames McCoy2021-09-20
| | | | | | | This is a workaround for not yet having fully correct Find* cmake modules for static builds. https://github.com/Tronic/cmake-modules/issues/3#issuecomment-624469020
* build: clean up / remove X_USE_STATIC (#10713)Daniel Hahler2019-08-07
| | | | | | | | This was discouraged (as an option) in 5b5d353151 [1], not enabled/used by default, and not working according to the comment in local.mk.example. Taken out of https://github.com/neovim/neovim/pull/10395. 1: https://github.com/neovim/neovim/pull/2465
* build: CMake: remove usage of USE_BUNDLED_X in main project (#10354)Daniel Hahler2019-06-28
| | | | | | | | | | | | | | | | | | The variables are not meant to be defined there really, but only with the third-party project. Using them, e.g. with the following, would actually result in libvterm not being found then: make CMAKE_EXTRA_FLAGS="-DUSE_BUNDLED_LIBVTERM=ON" \ DEPS_CMAKE_FLAGS="-DUSE_BUNDLED=OFF -DUSE_BUNDLED_LIBVTERM=ON" In https://github.com/neovim/neovim/pull/6357 they were renamed to `USE_BUNDLED_X` from `X_USE_BUNDLED`, but the above reasoning applies to the old names, too. Internally `CMAKE_PREFIX_PATH` is used to add the built/bundled third party packages for `find_package`, so there is no reason to e.g. query the values via `load_cache` for example from the third-party project.
* Change to not use library prefix on MSVCerw72018-05-23
|
* build: OpenBSD: libuv does not use KVM, do not link to it. (#6663)Edd Barrett2017-05-03
|
* cmake: USE_BUNDLED_X instead of X_USE_BUNDLED (#6357)Daniel Hahler2017-03-25
|
* cmake: Don't use check_library_exists for Win32 API librariesRui Abreu Ferreira2015-11-29
| | | | | | | | When building for X86 the CMake check_library_exists always fails to find functions from the Win32 API due to name mangling conventions. The convention for API functions is __stdcall and the CMake test code assumes __cdecl. Since these are libraries from the Windows API we can simply link against the libraries without checking for the functions.
* Windows: Link against libraries libuv needs on Windows.Rui Abreu Ferreira2015-09-09
|
* MSCV: FindLibUV: fix libname. #3261Rui Abreu Ferreira2015-08-31
|
* build: filter off libuv from PC_LIBUV_LIBRARIESJohn Szakmeister2015-02-24
| | | | | Otherwise, the -rdynamic that is being passed on the command line will require a dynamic link, even though we often want a static one.
* Removed unnecessary PATHS from cmake modulesRui Abreu Ferreira2014-07-08
| | | | | - DEPS_INSTALL_DIR is already set into CMAKE_PREFIX_PATH in the main CMakeLists.txt
* Append to CMAKE_PREFIX_PATH instead setting it outright.John Szakmeister2014-03-28
| | | | | Also, don't set it in the FindXxx cmake scripts--it's unnecessary, and it resets the value.
* Deal with the missing dependencies for libuv.John Szakmeister2014-03-21
| | | | | | Since libuv.pc is broken at the moment, try to determine libuv's dependencies ourselves. This ports most of the checks from libuv into our CMake build, and fixes the build on other unix platforms.
* Revamp the build system.John Szakmeister2014-03-21
| | | | | | | | | | | | | | | | | | | | | 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.
* CMake: add LibUV_USE_STATIC configuration variableRich Wareham2014-02-26
| | | | | | If LibUV_USE_STATIC is set then the static libuv library will be preferred to the shared library. This is useful when building with the bundled libuv but is less useful when building with a system libuv.
* prefer linking to static libuvRich Wareham2014-02-26
| | | | | | | | Explicitly try to find the static libuv library first. This might be considered a hack and if it weren't a single-use module it might be preferable to control static versus shared preferences with a configuration variable.
* automatically discover libuv in CMakeRich Wareham2014-02-26
Idiomatically discover if libuv is installed.