This SDK is no longer supported and it is maintained by Microsoft employees and external contributors in a best effort way (in their free time). To send events to Azure Event Hub in other languages please see the Azure Event Hub documentation, quickstarts section.
For use cases where connectivity to Event Hub is needed in a C development environment, please use uamqp-c or other AMQP C clients.
The Azure Event Hubs Client for C is a library specifically aimed at clients looking to send event data into an existing Event Hub. The library builds on the compact uAMQP library for AMQP 1.0 and we include build and usage instructions for a variety of Linux flavors and also for Windows.
As the primary audience for this library is the embedded devices development community, the library also provides some level of insulation against intermittent network availability interruptions common with devices connected via wireless radio networks of any kind.
The library supports sending individual events as well as batched event submission.
To maximize portability, the code is written in ANSI C (C99) and avoids any compiler extensions. The build output is a static library.b.
The library has a dependency on azure-uamqp-c and azure-c-shared-utility; those projects are external to this project, and referenced as git submodules.
When switching branches in this repository, remember to update the submodules by:
git submodule update --init --recursive
The build requires CMake 2.8.11 or better and a CMake supported C/C++ compiler and linker on the target platform. CMake will create all required files for building the library with the chosen tool chain.
- Create a directory named "build" and cd to "build".
- Configure your build by running:
Ex 1.
cmake ..Ex 2.cmake -Drun_unittests:BOOL=ON .. - Build. The build process will vary by platform; for Linux the default is "make".
Linux users please note that there are dependent packages that would need to be obtained prior to building this library. Please review and tailor the build_all/linux/setup.sh to suit your environment.
The build process will also build the available samples, which reside under samples for your review.
Specific instructions are available for the following platforms:
Several of these documents are known to be outdated.