-
Notifications
You must be signed in to change notification settings - Fork 60
/
README.txt
279 lines (214 loc) · 12.7 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
--------------------------------------------------------------------------
ActiveMQ CPP Library
--------------------------------------------------------------------------
ActiveMQ CPP is a messaging library that can use multiple protocols to
talk to a MOM (e.g. ActiveMQ).
1 Dependencies
--------------------------------------------------------------------------
There are several dependencies that need to be met in order to build and
install ActiveMQ-CPP on a Unix type system, the short list is shown below,
read the sections that follow for more detailed information. On Windows
you will not need the Auto Tools since the library is built using Microsft's
Visual Studio product.
Tool Recommended Version
-------------------------------
autoconf >= 2.61
automake >= 1.10
libtool >= 1.5.24
APR >= 1.3*
APR-Util >= 1.3* or higher
CPPUnit >= 1.10.2* ( 1.12.1 is recommended )
OpenSSL >= 0.9.8m* ( 1.0.0 or higher is recommended, this is an optional dependency)
* Requires that the Development package also be installed.
1.1 CppUnit
--------------------------------------------------------------------------
The package contains a complete set of CppUnit tests. In order for you to
build an run the tests, you will need to download and install the CppUnit
suite. See http://cppunit.sourceforge.net/cppunit-wiki
On Fedora, type the following:
sudo yum install cppunit cppunit-devel
On Debian/Ubuntu, type the following:
sudo apt-get install libcppunit-dev
Make sure that the paths to the installed CppUnit library and includes are
visible in your current shell before you try building the tests.
Windows users will need to build the CppUnit library using the CPPUnit
MSVC project files. A discussion of the build process can be found
on the CPPUnit wiki under:
http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1
This covers both MSVC along with many other platforms and tool suites.
The included Visual Studio projects are configured with the assumption
that you will configure Visual Studio with the locations of the Platform
SDK and the CPPUnit and APR libraries and headers.
1.2 APR and APR Util
-------------------------------------------------------------------------
The build requires the APR library and the APR-Util. These libraries can
be obtained from the APR site at: http://apr.apache.org/ See the
documentation there on how to build these libraries for your platform. On
many Unix system the libraries can be installed using the systems package
installer.
The Library has been tested using version v1.3 and higher of the APR libs,
the older 0.9 version will definitely not work with this library.
Many of the Unix type OS'es currently shipping include APR 1.2.x and
APR-Util 1.2.x, this implies that you will need to build and install APR from
the source download at Apache.
-----------------------------------------------------------------------
|MacOS X Note: |
| If you have installed APR and APR-Util via MacPorts |
| (http://www.macports.org/) and you are building ActiveMQ-CPP from |
| source, you will need to specify the location of the APR libraries |
| to the configure script. This is easy to do and only requires one |
| extra option for compilation. An example of this is shown below |
| using the standard location for these libraries as installed by |
| MacPorts: |
| |
| $ ./configure \ |
| --with-apr=/opt/local/var/macports/software/apr/1.3.3_0/opt/local/ |
| |
| Please notice that this is simply a single option to the |
| configure script that has been broken into two lines by escaping |
| the newline character to fit the formatting of this file. |
| |
| If you have manually compiled and installed the APR libraries into |
| a custom location, then you will need to point to that location |
| using the argument above. |
-----------------------------------------------------------------------
1.3 OpenSSL
--------------------------------------------------------------------------
If you wish to use the SSL Transport then you will need to have OpenSSL and
its includes installed on your system. We recommend that you use version 1.0.0
or higher for best performance and security, but version from 0.9.8 are also
known to work. The autoconf script will search for the library and enabled support
automatically if it is found.
You can disable the OpenSSL checks in the configure script with the --disable-ssl
option or you can specify a custom location for the OpenSSL package with the
--with-openssl option. See the --help option on the configure script for more
information.
On Windows you need to obtain an OpenSSL binary package and place the libraries on
the system path or in the System32 directory. In the Visual Studio project you must
add the HAVE_OPENSSL flag to the preprocessor directives and add the paths for the
includes and libraries so that the compiler and linker can find them.
1.4 GNU Build System (for building on Unix/Linux/OS X)
--------------------------------------------------------------------------
To Generate the ./configure script use to create the Makefiles, you need
the following software installed:
Tool Recommended Version
-------------------------------
autoconf >= 2.61
automake >= 1.10
libtool >= 1.5.24
On Debian/Ubuntu, multiple versions of autoconf and automake are available
in separate packages. If you have multiple versions of autoconf or automake
installed on your system, you may have to configure the versions to use
using /usr/sbin/update-alternatives.
-----------------------------------------------------------------------
|Ubuntu Note: |
| |
|In order to build you will need the Build Essentials Package |
| |
| sudo apt-get install build-essential |
-----------------------------------------------------------------------
2 Building on Unix/Linux/OS X
--------------------------------------------------------------------------
-----------------------------------------------------------------------
|Solaris 10 Note: CppUnit might not build until you correct the file |
| libstdc++.la to contain the correct data, see this discussion: |
| http://forum.sun.com/jive/thread.jspa?threadID=73150 |
| Also you must pass --enable-shared=no for Solaris GCC builds |
| For Solaris builds using the Sun Compiler you must set the env |
| values CC and CXX to point to the cc and CC commands respectively. |
-----------------------------------------------------------------------
The configure script will customize the way the software is built and
installed into your system along with detecting the available libraries
that have been installed. To use the default configuration just run:
./configure
For more help on how to customize the build configuration, run:
./configure --help
Once the configure script has run successfully, you are ready to build.
Run:
make
This will build all of the core ActiveMQ CPP source code. To build and
install the code into the system directories, run:
make install
You will have to become the superuser in order to be able to install the
files.
** A Note For ActiveMQ-CPP Developers **
If you need to make any changes to the configure.ac or any of the included
m4 files then you need to regenerate the configure script.
./autogen.sh
This should be run the first time and any time you change configure.ac or
any of the Makefile.am files.
-----------------------------------------------------------------------
|MacOS X Note: |
| Make sure to set the LIBTOOLIZE environment variable to point to |
| /usr/bin/glibtoolize for the build to complete successfully. Below |
| is an example: |
| |
| $ export LIBTOOLIZE=/usr/bin/glibtoolize |
| |
| If you do not use this environment variable you will encounter an |
| error stating: |
| |
| Can't exec "libtoolize": No such file or directory at |
| /opt/local/share/autoconf/Autom4te/FileUtils.pm line 290... |
-----------------------------------------------------------------------
3 Doxygen
--------------------------------------------------------------------------
To generate the Doxygen documentation for the project, just run:
make doxygen-run
4 Running Tests
--------------------------------------------------------------------------
4.1 Unit Tests
--------------------------------------------------------------------------
In order to build and run the suite of unit tests, run:
make check
This will verify that the library is functioning correctly on the target
platform. In addition, it will generate the integration tests binary.
4.2 Integration Tests
--------------------------------------------------------------------------
The library also contains a set of tests that are run against a real AMQ
broker. These allow you to validate this distribution of ActiveMQ CPP
against your broker. Running these without a broker will result in failed
tests. The tests currently hard-code the broker url to be
tcp://localhost:61613 for Stomp and tcp://localhost:61616 for Openwire.
The integration tests are built via "make check". To run them, first
start a broker and then
cd src/test-integration
./activemq-test-integration
This will take quite some time to complete, so be patient. It is recommended
that you restart the broker between successive runs of the integration tests.
5 Example
--------------------------------------------------------------------------
There are example applications that ship with the distribution in
src/examples. The examples are compiled by default with the "make"
command on Unix systems. Only one sample is included in the Visual Studio
projects supplied, the others can be easily added by examining the settings
of the one supplied.
6 Notes for Windows users
--------------------------------------------------------------------------
We do not support using the GNU compiler on Windows, using the Cygwin package
or the MinGW platform, several issues with sockets and threading were found to
exist when trying to use these solutions.
However we do support using the MSVC compiler on Windows.
There are a couple or things that you will need to setup to ensure that
the MSVC compile succeeds.
* When linking your application to the DLL version of the ActiveMQ-CPP library
you must link your app the the same runtime version that the DLL is linked to,
otherwise your application will cause heap corruption when you delete objects
that are created in the ActiveMQ-CPP DLL's heap.
* You need to download and install the Platform SDK if you don't have it
installed already. On machines where you intend to use the built libraries
and executable you will also need to install the MS Redistributable for the
version of Visual Studio which you used to build the library.
* Ensure that the path to you MSVC install is set in the PATH env variable.
You can test this by typing cl.exe at the command line, if you get an
error complaining that its not found, then you'll need to fix your PATH.
* The Project files reference the CPPUnit libraries for the Integration and
Unit tests builds. In order for these to build correctly you must
either configure the global settings in Visual Studio for include and library
folders or add new settings to each of the projects in the solution to point
to these locations.
* The Project files reference the APR libraries for the Integration and
Unit tests builds. In order for these to build correctly you must
either configure the global settings in Visual Studio for include and library
folders or add new settings to each of the projects in the solution to point
to these locations.