luo980/libuv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Cross-platform asynchronous I/O
1,605 Commits 13 Branches 240 Tags 29 MiB
C 97%
M4 1.2%
CMake 0.9%
Makefile 0.7%
27cd5f03ef
Go to file
Ben Noordhuis 27cd5f03ef linux: fix accept4() ENOSYS detection on i386 
accept4() piggybacks on the socketcall() on i386. socketcall() has the flaw
that it returns EINVAL instead of ENOSYS when the operation is not supported.

The problem is that accept4() also returns EINVAL when its flag argument is
invalid.

Try to discern between the two failure cases to the best of our abilities.
2012-06-29 02:11:45 +02:00
build
include unix: map ENODEV to UV_ENODEV 2012-06-26 17:33:29 +02:00
src linux: fix accept4() ENOSYS detection on i386 2012-06-29 02:11:45 +02:00
test win: map ERROR_PRIVILEGE_NOT_HELD to UV_EPERM 2012-06-25 16:37:08 +02:00
.gitignore
.mailmap
.travis.yml
AUTHORS
common.gypi
config-mingw.mk unix, windows: add stat() based file watcher 2012-05-31 20:32:24 +02:00
config-unix.mk unix, windows: add stat() based file watcher 2012-05-31 20:32:24 +02:00
gyp_uv
LICENSE
Makefile
README.md
uv.gyp bench: add thread pool I/O benchmark 2012-06-21 22:40:17 +02:00
vcbuild.bat

README.md

libuv Build Status

libuv is a new platform layer for Node. Its purpose is to abstract IOCP on Windows and libev 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 c-ares or 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

Documentation

See include/uv.h.

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

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.