||10 years ago|
|src||10 years ago|
|.gitignore||10 years ago|
|COPYING||10 years ago|
|Makefile.am||10 years ago|
|README.md||10 years ago|
|autogen.sh||10 years ago|
|configure.ac||10 years ago|
|evcon-ev.pc.in||10 years ago|
|evcon-event.pc.in||10 years ago|
|evcon-glib.pc.in||10 years ago|
|evcon.pc.in||10 years ago|
|libevcon-ev0.symbols||10 years ago|
|libevcon-event0.symbols||10 years ago|
|libevcon-glib0.symbols||10 years ago|
|libevcon0.symbols||10 years ago|
evon is a generic wrapper library that sits between libraries that need socket (file descriptor), timeout and (thread safe) asynchronous events, and an application that wants to use the library.
Should work on all POSIX compatible platforms.
- read and write events for asynchronous file descriptors (sockets)
- simple timeout events
- (thread safe) asynchronous events (notifications - for example from other threads, that wakeup the event loop)
You want to write an application that uses two different event based libraries; if these libraries don't use the same event loop (say X uses libev and Y libevent) you will have difficulties using them - you could give each library its own thread for example, but embedding one event loop in another is usually not easy.
If the libraries were built against evcon, you could use any event loop - if there is no backend for it yet, you probably can write one.
src/tests/evcon-echo.h for an example "library", and
src/tests/evcon-test-*.c for how to use them in an application.
Building from git
Run the following in the source directory to prepare the build system:
You will need automake and autoconf for this.
All backends need glib (>= 2.14). The libev backend needs libev >= 4, the libevent backend needs libevent >= 2.
Build in a sub directory:
mkdir build cd build ../configure make check
Install (probably has to be run as root):
As always it is recommended to use a package system to install files instead (dpkg, rpm, ...).