# Linking Libevent Windows C Client
**URL:** https://discuss.aerospike.com/t/linking-libevent-windows-c-client/4958
**Category:** C Client Library
**Created:** [February 16, 2018, 8:35pm UTC](https://discuss.aerospike.com/t/linking-libevent-windows-c-client/4958 "2018-02-16T20:35:45Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@yncraig](https://discuss.aerospike.com/u/yncraig)
#### Post date: [February 16, 2018, 8:35pm UTC](https://discuss.aerospike.com/t/linking-libevent-windows-c-client/4958/1 "2018-02-16T20:35:45Z")
Background story: Libevent is currently running on our platform. Aerospike Windows Libevent Client includes already have associated headers included.
#define EVENT\_\_VERSION “2.1.8-beta”
Why is beta version libevent is used here? Which libevent version should I build to be compatible with it?
Thanks
---
### Author:  [@Brian](https://discuss.aerospike.com/u/Brian)
#### Post date: [February 16, 2018, 10:40pm UTC](https://discuss.aerospike.com/t/linking-libevent-windows-c-client/4958/2 "2018-02-16T22:40:08Z")
The libevent included in the Aerospike Windows C client was built from the `release-2.1.8-stable` tag of libevent github repo ([GitHub - libevent/libevent at release-2.1.8-stable](https://github.com/libevent/libevent/tree/release-2.1.8-stable)).
The libevent `README.md` states that EVENT\_STAGE\_VERSION defaults to `beta` when building using cmake.
```auto
# set EVENT_STAGE_VERSION
EVENT__STAGE_VERSION:STRING=beta
```
I did not change this variable when building, so `beta` appeared in the version string in the generated `event-config.h`.
I verified that the libevent C files and non-auto-generated header files are identical between github `release-2.1.8-stable` tag and `libevent-2.1.8-stable.tar.gz` on the libevent website.
It’s not possible to build on Visual Studio using `libevent-2.1.8-stable.tar.gz` because the required cmake files (CMakeLists.txt, …) do not exist in this tarball.
In summary, you should build with libevent 2.1.8-stable.