Updated README.md to reflect changes.

This commit is contained in:
Aart Stuurman 2018-01-26 23:50:41 +01:00
parent b558b8cac6
commit f7e8cf5414
1 changed files with 95 additions and 82 deletions

View File

@ -62,20 +62,34 @@ Then check out our other commercial and open source solutions:
INSTALLING
==========
There are two methods to compile AMQP-CPP, CMake and Make. CMake is platform portable, but the Makefile only works on Linux.
## CMake
The CMake file supports both building and installing. You can choose not to use the install functionality, and instead to manually use the build output at bin/. Keep in mind that the TCP module is only supported for Linux. An example install method would be:
``` bash
mkdir build
cd build
cmake .. [-DBUILD_SHARED] [-DLINUX_TCP]
cmake --build .. --target install
```
If you are on some kind of Linux environment, installing the library is as easy
### BUILD_SHARED
Default OFF
ON: Build shared library
OFF: Build static library
### LINUX_TCP
Default OFF
ON: Build linux-only TCP module
OFF: Do not build the module.
## Make
Installing the library is as easy
as running `make` and `make install`. This will install the full version of
the AMQP-CPP, including the system specific TCP module. If you do not need the
additional TCP module (because you take care of handling the network stuff
yourself), you can also compile a pure form of the library. Use `make pure`
and `make install` for that.
For users on a non-Linux environment: this library is known to work on your
environment too (after all, it does not do any operating specific system calls),
but it might take some extra effort to get your compiler to compile it. Please
send in your pull requests once you have it running, so that others can benefit
from your experiences.
When you compile an application that uses the AMQP-CPP library, do not
forget to link with the library. For gcc and clang the linker flag is -lamqpcpp.
If you use the fullblown version of AMQP-CPP (with the TCP module), you also
@ -992,4 +1006,3 @@ class that can be directly plugged into libev, libevent and libuv event loops.
For performance reasons, we need to investigate if we can limit the number of times
an incoming or outgoing messages is copied.