Cross-platform asynchronous I/O
Go to file
Alexis Campailla 68ac0a68e7 windows: fix netmask detection
uv_interface_addresses was using the linked list pointed to by
the FirstPrefix member of IP_ADAPTER_ADDRESSES in order to compute the
network prefix / network mask.

This was flawed in several ways:
- FirstPrefix can be NULL, and we would crash.
- On Windows Vista and later, the prefix list includes three IP adapter prefixes
  for each IP address assigned to the adapter. We were assuming a 1:1 mapping
  with the unicast address list.
- Even on Windows versions (i.e. XP) where the prefix list is supposed to have
  one and only one element for each unicast address, the order of the two lists
  is not guaranteed to be the same.

This fix was inspired and adapted from a commit in the Chromium project:
https://codereview.chromium.org/25167002/diff/6001/net/base/net_util_win.cc

See MSDN article for reference:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa366058(v=vs.85).aspx

Excerpt from MSDN below:

In addition, the linked IP_ADAPTER_UNICAST_ADDRESS structures pointed to
by the FirstUnicastAddress member and the linked IP_ADAPTER_PREFIX
structures pointed to by the FirstPrefix member are maintained as separate
internal linked lists by the operating system. As a result, the order of
linked IP_ADAPTER_UNICAST_ADDRESS structures pointed to by the
FirstUnicastAddress member does not have any relationship with the order
of linked IP_ADAPTER_PREFIX structures pointed to by the FirstPrefix member.

On Windows Vista and later, the linked IP_ADAPTER_PREFIX structures pointed to
by the FirstPrefix member include three IP adapter prefixes for each IP address
assigned to the adapter. These include the host IP address prefix, the subnet
IP address prefix, and the subnet broadcast IP address prefix. In addition, for
each adapter there is a multicast address prefix and a broadcast address prefix.
2014-10-13 23:18:14 +02:00
docs unix, windows: add uv_fs_access() 2014-10-13 10:23:53 +02:00
img img: add logo files 2014-07-20 18:24:28 +02:00
include unix, windows: add uv_fs_access() 2014-10-13 10:23:53 +02:00
m4 ignore: include m4 files which are created manually 2014-09-17 22:51:04 +02:00
samples gyp: qualify library variable 2014-02-05 21:29:25 +04:00
src windows: fix netmask detection 2014-10-13 23:18:14 +02:00
test unix, windows: add uv_fs_access() 2014-10-13 10:23:53 +02:00
.gitignore ignore: ignore Xcode project and workspace files 2014-09-17 22:50:40 +02:00
.mailmap 2014.08.20, Version 0.11.29 (Unstable) 2014-08-19 11:03:51 -04:00
android-configure build: update android toolchain 2014-02-21 18:54:52 +01:00
AUTHORS 2014.08.20, Version 0.11.29 (Unstable) 2014-08-19 11:03:51 -04:00
autogen.sh build: fix automake serial-tests check again 2013-08-17 15:08:49 +02:00
ChangeLog version: now working on 1.0.0-rc2 2014-09-18 18:48:09 +02:00
checksparse.sh Revert "inet: allow scope in uv_inet_pton ip6 check" 2014-04-14 15:13:20 +04:00
common.gypi gyp: qualify library variable 2014-02-05 21:29:25 +04:00
configure.ac build: add DragonFly BSD support in autotools 2014-09-27 11:25:59 +02:00
CONTRIBUTING.md doc: update references to current stable branch 2014-09-22 20:37:45 -04:00
gyp_uv.py build: handle platforms without multiprocessing.synchronize 2014-07-31 10:12:58 +02:00
libuv.pc.in build: add required libraries to libuv.pc.in 2014-03-02 11:46:32 +01:00
LICENSE android: add support of ifaddrs in android 2014-03-16 23:16:25 +01:00
Makefile.am build: add DragonFly BSD support in autotools 2014-09-27 11:25:59 +02:00
Makefile.mingw unix, windows: use the same threadpool implementation 2014-06-27 14:27:04 +02:00
README.md doc: fix punctuation and grammar in README 2014-10-06 09:03:25 +02:00
uv.gyp build, gyp: set xcode flags 2014-09-17 22:52:25 +02:00
vcbuild.bat Merge branch 'v0.10' 2014-06-25 10:31:21 +02:00

libuv

Overview

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

Versioning

Starting with version 1.0.0 libuv follows the semantic versioning scheme. The API change and backwards compatiblity rules are those indicated by SemVer. libuv will keep a stable ABI across major releases.

Community

Documentation

Official API documentation

Located in the docs/ subdirectory. It uses the Sphinx framework, which makes it possible to build the documentation in multiple formats.

Show different supported building options:

$ make help

Build documentation as HTML:

$ make html

Build documentation as man pages:

$ make man

Build documentation as ePub:

$ make epub

NOTE: Windows users need to use make.bat instead of plain 'make'.

Documentation can be browsed online here.

Other resources

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

First, Python 2.6 or 2.7 must be installed 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

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 -ARCHS="x86_64" -project uv.xcodeproj \
     -configuration Release -target All

Note to OS X users:

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
$ 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.

Running tests

Run:

$ ./gyp_uv.py -f make
$ make -C out
$ ./out/Debug/run-tests

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.

Patches

See the guidelines for contributing.