$ ./configure $ make $ make verify # (optional) $ sudo make install
The following Libevent specific Cmake variables ar as follows (the values being the default).
More variables can be found by running
$ md build && cd build $ cmake -G "Visual Studio 10" .. # Or whatever generator you want to use cmake --help for a list. $ start libevent.sln
$ mkdir build && cd build $ cmake .. # Default to Unix Makefiles. $ make $ make verify # (optional)
To build libevent, type
$ ./configure && make
(If you got libevent from the git repository, you will first need to run the included "autogen.sh" script in order to generate the configure script.)
You can run the regression tests by running
$ make verify
Install as root via
$ make install
Before reporting any problems, please run the regression tests.
To enable the low-level tracing build the library as:
$ CFLAGS=-DUSE_DEBUG ./configure [...]
Standard configure flags should work. In particular, see:
--disable-shared Only build static libraries --prefix Install all files relative to this directory.
The configure script also supports the following flags:
--enable-gcc-warnings Enable extra compiler checking with GCC. --disable-malloc-replacement Don't let applications replace our memory management functions --disable-openssl Disable support for OpenSSL encryption. --disable-thread-support Don't support multithreaded environments.
(Note that autoconf is currently the most mature and supported build enviroment for libevent; the cmake instructions here are new and experimental, though they should be solid. We hope that cmake will still be supported in future versions of Libevent, and will try to make sure that happens.)
First of all install .
To build libevent using Microsoft Visual studio open the "Visual Studio Command prompt" and type:
$ mkdir build && cd build
$ cmake -G "Visual Studio 10" .. # Or whatever generator you want to use cmake --help for a list.
$ start libevent.sln
In the above, the ".." refers to the dir containing the Libevent source code. You can build multiple versions (with different compile time settings) from the same source tree by creating other build directories.
It is highly recommended to build "out of source" when using CMake instead of "in source" like the normal behaviour of autoconf for this reason.
The "NMake Makefiles" CMake generator can be used to build entirely via the command line.
To get a list of settings available for the project you can type:
$ cmake -LH ..
CMake also provides a GUI that lets you specify the source directory and output (binary) directory that the build should be placed in.
To build Libevent with OpenSSL support you will need to have OpenSSL binaries available when building, these can be found here:
For the latest released version of Libevent, see the official website at .
There's a pretty good work-in-progress manual up at .
For the latest development versions of Libevent, access our Git repository via
$ git clone https://github.com/libevent/libevent.git
You can browse the git repository online at:
To report bugs, issues, or ask for new features:
OK, those are not really patches You fork, modify, and hit the "Create Pull Request" button. You can still submit normal git patchs via the mailing list.
Bugs, Features [RFC], and Issus: https://github.com/libevent/libevent/issues
Or you can do it via the mailing list.
There's also a libevent-users mailing list for talking about Libevent use and development:
The following people have helped with suggestions, ideas, code or fixing bugs:
If we have forgotten your name, please contact us.