You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libuv is a multi-platform support library with a focus on asynchronous I/O. It
was primarily developed for use by Node.js, but it's also
used by Luvit, Julia,
pyuv, and others.
Feature highlights
Full-featured event loop backed by epoll, kqueue, IOCP, event ports.
Asynchronous TCP and UDP sockets
Asynchronous DNS resolution
Asynchronous file and file system operations
File system events
ANSI escape code controlled TTY
IPC with socket sharing, using Unix domain sockets or named pipes (Windows)
Child processes
Thread pool
Signal handling
High resolution clock
Threading and synchronization primitives
Versioning
Starting with version 1.0.0 libuv follows the semantic versioning
scheme. The API change and backwards compatibility rules are those indicated by
SemVer. libuv will keep a stable ABI across major releases.
libuv is licensed under the MIT license. Check the LICENSE file.
The documentation is licensed under the CC BY 4.0 license. Check the LICENSE-docs file.
Starting with libuv 1.7.0, binaries for Windows are also provided. This is to
be considered EXPERIMENTAL.
Before verifying the git tags or signature files, importing the relevant keys
is necessary. Key IDs are listed in the
MAINTAINERS
file, but are also available as git blob objects for easier use.
Git tags are signed with the developer's key, they can be verified as follows:
$ git verify-tag v1.6.1
Starting with libuv 1.7.0, the tarballs stored in the
downloads site are signed and an accompanying
signature file sit alongside each. Once both the release tarball and the
signature file are downloaded, the file can be verified as follows:
$ gpg --verify libuv-1.7.0.tar.gz.sign
Build Instructions
For GCC there are two build methods: via autotools or via GYP.
GYP is a meta-build system which can generate MSVS, Makefile, and XCode
backends. It is best used for integration into other projects.
To build with autotools:
$ sh autogen.sh
$ ./configure
$ make
$ make check
$ make install
Windows
Prerequisites:
Python 2.6 or 2.7 as it is required
by GYP.
If python is not in your path, set the environment variable PYTHON to its
location. For example: set PYTHON=C:\Python27\python.exe
Visual Studio 2015 Update 3, all editions
including the Community edition (remember to select
"Common Tools for Visual C++ 2015" feature during installation).
Visual Studio 2017, any edition (including the Build Tools SKU).
Required Components: "MSbuild", "VC++ 2017 v141 toolset" and one of the
Windows SDKs (10 or 8.1).
Basic Unix tools required for some tests,
Git for Windows includes Git Bash
and tools which can be included in the global PATH.
To build, launch a git shell (e.g. Cmd or PowerShell), run vcbuild.bat
(to build with VS2017 you need to explicitly add a vs2017 argument),
which will checkout the GYP code into build/gyp, generate uv.sln
as well as the necesery related project files, and start building.
> vcbuild
Or:
> vcbuild vs2017
To run the tests:
> vcbuild test
To see all the options that could passed to vcbuild:
Make sure that you specify the architecture you wish to build for in the
"ARCHS" flag. You can specify more than one by delimiting with a space
(e.g. "x86_64 i386").
Android
Run:
$ source ./android-configure NDK_PATH gyp [API_LEVEL]
$ make -C out
The default API level is 24, but a different one can be selected as follows:
$ source ./android-configure ~/android-ndk-r15b gyp 21
$ make -C out
Note for UNIX users: compile your project with -D_LARGEFILE_SOURCE and
-D_FILE_OFFSET_BITS=64. GYP builds take care of that automatically.
Using Ninja
To use ninja for build on ninja supported platforms, run:
AIX support for filesystem events requires the non-default IBM bos.ahafs
package to be installed. This package provides the AIX Event Infrastructure
that is detected by autoconf.
IBM documentation
describes the package in more detail.
AIX support for filesystem events is not compiled when building with gyp.