Cross-platform asynchronous I/O
Go to file
Ben Noordhuis b1b931de4e fsevents: use native character encoding file paths
Create file paths with CFStringCreateWithFileSystemRepresentation(),
not CFStringCreateWithCString().

Reapplies 3780e12 ("fsevents: support japaneese characters in path")
from the v0.10 branch.  Was dropped in the last v0.10 -> master merge
for failing to apply.
2013-11-08 14:03:57 +01:00
include unix: return exec errors from uv_spawn, not async 2013-11-07 22:10:38 +01:00
m4 build: add DTrace detection for autotools 2013-07-03 16:04:01 -07:00
src fsevents: use native character encoding file paths 2013-11-08 14:03:57 +01:00
test Merge remote-tracking branch 'origin/v0.10' 2013-11-08 03:44:31 +01:00
.gitignore
.mailmap
android-configure
AUTHORS
autogen.sh
ChangeLog
checksparse.sh Merge remote-tracking branch 'origin/v0.10' 2013-11-08 03:44:31 +01:00
common.gypi
configure.ac
gyp_uv.py
LICENSE
Makefile.am
Makefile.mingw
README.md
uv.gyp Merge remote-tracking branch 'origin/v0.10' 2013-11-08 03:44:31 +01:00
vcbuild.bat

libuv

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 Mozilla's Rust language, 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

Community

Documentation

Build Instructions

For GCC there are two methods building: 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

First, Python 2.6 or 2.7 must be installed as it is required by GYP.

Also, the directory for the preferred Python executable must be specified by the PYTHON or Path environment variables.

To build with Visual Studio, launch a git shell (e.g. Cmd or PowerShell) and run vcbuild.bat which will checkout the GYP code into build/gyp and generate uv.sln as well as related project files.

To have GYP generate build script for another system, checkout GYP into the project tree manually:

$ mkdir -p build
$ git clone https://git.chromium.org/external/gyp.git build/gyp

Unix

Run:

$ ./gyp_uv.py -f make
$ make -C out

OS X

Run:

$ ./gyp_uv.py -f xcode
$ xcodebuild -project uv.xcodeproj -configuration Release -target All

Android

Run:

$ source ./android-configure NDK_PATH gyp
$ 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.

Supported Platforms

Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW. Consider using Visual Studio Express 2010 or later if you do not have a full Visual Studio license.

Linux using the GCC toolchain.

OS X using the GCC or XCode toolchain.

Solaris 121 and later using GCC toolchain.