Cross-platform asynchronous I/O
Go to file
Bert Belder 2e4488f35a windows: improve / fix uv_interface_addresses
* If GetAdaptersAddresses() failed, it would return UV_OK nonetheless,
  but the `adresses` and `count` out parameters would not be set.

* When adapters were enabled or added in between the two
  GetAdaptersAddresses() calls, it would fail.

* In case of an out of memory situation, libuv would crash with a fatal
  error.

* All interface information is now stored in a single heap-allocated
  area.
2012-12-04 14:04:37 +01:00
include unix: change uv_backend_timeout() prototype 2012-11-28 17:02:30 +01:00
src windows: improve / fix uv_interface_addresses 2012-12-04 14:04:37 +01:00
test test: fix finished consumer number check 2012-11-29 15:40:00 +01:00
.gitignore Remove *.mk and *.Makefile from .gitignore list 2012-11-28 21:32:43 +01:00
.mailmap
.travis.yml
AUTHORS
common.gypi
config-mingw.mk
config-unix.mk build: fix dragonflybsd build, link with libkvm 2012-11-19 23:57:29 +01:00
gyp_uv
LICENSE unix: remove libev 2012-11-16 17:33:29 +01:00
Makefile build: fix make test on darwin and sunos 2012-11-10 01:43:42 +01:00
README.md unix: remove dependency on libev 2012-11-16 17:33:25 +01:00
uv.gyp unix: add uv_backend_fd() and uv_backend_timeout() 2012-11-28 16:30:50 +01:00
vcbuild.bat

libuv Build Status

libuv is a new platform layer for Node. Its purpose is to abstract IOCP on Windows and epoll/kqueue/event ports/etc. on Unix systems. We intend to eventually contain all platform differences in this library.

http://nodejs.org/

Features

  • Non-blocking TCP sockets

  • Non-blocking named pipes

  • UDP

  • Timers

  • Child process spawning

  • Asynchronous DNS via uv_getaddrinfo.

  • Asynchronous file system APIs uv_fs_*

  • High resolution time uv_hrtime

  • Current executable path look up uv_exepath

  • Thread pool scheduling uv_queue_work

  • ANSI escape code controlled TTY uv_tty_t

  • File system events Currently supports inotify, ReadDirectoryChangesW and kqueue. Event ports in the near future. uv_fs_event_t

  • IPC and socket sharing between processes uv_write2

Community

Documentation

Build Instructions

For GCC (including MinGW) there are two methods building: via normal makefiles 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. The old (more stable) system is using Makefiles.

To build via Makefile simply execute:

make

To build with Visual Studio run the vcbuilds.bat file which will checkout the GYP code into build/gyp and generate the uv.sln and related files.

Windows users can also build from cmd-line using msbuild. This is done by running vcbuild.bat from Visual Studio command prompt.

To have GYP generate build script for another system you will need to checkout GYP into the project tree manually:

svn co http://gyp.googlecode.com/svn/trunk build/gyp

Unix users run

./gyp_uv -f make
make

Macintosh users run

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

Note for Linux users: compile your project with -D_GNU_SOURCE when you include uv.h. GYP builds take care of that automatically. If you use autotools, add a AC_GNU_SOURCE declaration to your configure.ac.

Supported Platforms

Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW.

Linux 2.6 using the GCC toolchain.

MacOS using the GCC or XCode toolchain.

Solaris 121 and later using GCC toolchain.