Caleb James DeLisle 7a79e93000 applied patches to libuv | há 11 anos atrás | |
---|---|---|
.. | ||
include | há 11 anos atrás | |
src | há 11 anos atrás | |
test | há 11 anos atrás | |
.gitignore | há 11 anos atrás | |
.mailmap | há 11 anos atrás | |
AUTHORS | há 11 anos atrás | |
ChangeLog | há 11 anos atrás | |
LICENSE | há 11 anos atrás | |
Makefile | há 11 anos atrás | |
README.md | há 11 anos atrás | |
build.mk | há 11 anos atrás | |
checksparse.sh | há 11 anos atrás | |
common.gypi | há 11 anos atrás | |
config-mingw.mk | há 11 anos atrás | |
config-unix.mk | há 11 anos atrás | |
gyp_uv | há 11 anos atrás | |
uv.gyp | há 11 anos atrás | |
uv_mingw32.patch | há 11 anos atrás | |
uv_so_reuseport.patch | há 11 anos atrás | |
vcbuild.bat | há 11 anos atrás |
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.
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
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 system is using plain GNU Makefiles.
To build via Makefile simply execute:
make
MinGW users should run this instead:
make PLATFORM=mingw
Out-of-tree builds are supported:
make builddir_name=/path/to/builddir
To build with Visual Studio run the vcbuild.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, make sure that you have Python 2.6 or 2.7 installed, then checkout GYP into the project tree manually:
mkdir -p build
svn co http://gyp.googlecode.com/svn/trunk build/gyp
Or:
mkdir -p build
git clone https://git.chromium.org/external/gyp.git build/gyp
Unix users run
./gyp_uv -f make
make -C out
Macintosh users run
./gyp_uv -f xcode
xcodebuild -project uv.xcodeproj -configuration Release -target All
Note for UNIX users: compile your project with -D_LARGEFILE_SOURCE
and
-D_FILE_OFFSET_BITS=64
. GYP builds take care of that automatically.
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
.
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.