ea12428db6
After update [1] of the Visual Studio 2019 image cmake unable to find
path to the c compiler [2]:
cmake : CMake Error at CMakeLists.txt:47 (project):
At line:1 char:1
+ cmake -G 'Visual Studio 16 2019' -A x64 ..
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (CMake Error at ...t:47 (project)::String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
The CMAKE_C_COMPILER:
C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
is not a full path to an existing compiler tool.
[1]: https://github.com/appveyor/ci/issues/3231
https://www.appveyor.com/updates/2019/12/09/
[2]: https://ci.appveyor.com/project/libevent/libevent/builds/29431286/job/a68h7dn9rcride9g
1. BUILDING AND INSTALLATION
Autoconf
$ ./configure
$ make
$ make verify # (optional)
$ sudo make install
See Documentation/Building#Autoconf for more information
CMake (Windows)
Install CMake: https://www.cmake.org
$ md build && cd build
$ cmake -G "Visual Studio 10" .. # Or use any generator you want to use. Run cmake --help for a list
$ cmake --build . --config Release # Or "start libevent.sln" and build with menu in Visual Studio.
See Documentation/Building#Building on Windows for more information
CMake (Unix)
$ mkdir build && cd build
$ cmake .. # Default to Unix Makefiles.
$ make
$ make verify # (optional)
See Documentation/Building#Building on Unix (With CMake) for more information
2. USEFUL LINKS:
For the latest released version of Libevent, see the official website at http://libevent.org/ .
There's a pretty good work-in-progress manual up at http://www.wangafu.net/~nickm/libevent-book/ .
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:
https://github.com/libevent/libevent
To report bugs, issues, or ask for new features:
Patches: https://github.com/libevent/libevent/pulls
OK, those are not really patches. You fork, modify, and hit the "Create Pull Request" button. You can still submit normal git patches via the mailing list.
Bugs, Features [RFC], and Issues: 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:
http://archives.seul.org/libevent/users/
3. ACKNOWLEDGMENTS
The following people have helped with suggestions, ideas, code or fixing bugs.