Skip to content

Instantly share code, notes, and snippets.

@israelshirk
Created May 13, 2015 20:03
Show Gist options
  • Save israelshirk/039300e75a2c4cbd7a13 to your computer and use it in GitHub Desktop.
Save israelshirk/039300e75a2c4cbd7a13 to your computer and use it in GitHub Desktop.
ActiveMQ-cpp 3.8.2 spec file for RHEL6, no doc
Name: activemq-cpp
Version: 3.8.2
Release: 1%{?dist}
Summary: C++ Implementation of a JMS style Messaging Client
Group: Development/Libraries
License: ASL 2.0
URL: http://activemq.apache.org/cms/
Source0: http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-%{version}-src.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
#BuildRequires: doxygen
BuildRequires: graphviz
BuildRequires: automake >= 1.10
BuildRequires: autoconf >= 2.61
BuildRequires: libtool >= 1.5.24
BuildRequires: apr-devel%{?_isa} >= 1.3
BuildRequires: cppunit-devel%{?_isa} >= 1.10.2
BuildRequires: openssl-devel%{?_isa} >= 0.98.0
%description
activemq-cpp is a JMS-like API for C++ for interfacing with Message
Brokers such as Apache ActiveMQ. C++ messaging service helps to make your
C++ client code much neater and easier to follow. To get a better feel for
CMS try the API Reference or the getting started page on the ActiveMQ-CPP
website.
ActiveMQ-CPP is a client only library, a message broker such as Apache
ActiveMQ is still needed for your clients to communicate with one another.
%package devel
Summary: Development files for using the %{name} library
Group: Development/Libraries
Requires: %{name} = %{version}-%{release}
Requires: pkgconfig
%description devel
activemq-cpp is a JMS-like API for C++ for interfacing with Message
Brokers such as Apache ActiveMQ. C++ messaging service helps to make your
C++ client code much neater and easier to follow. To get a better feel for
CMS try the API Reference or the getting started page on the ActiveMQ-CPP
website.
ActiveMQ-CPP is a client only library, a message broker such as Apache
ActiveMQ is still needed for your clients to communicate with one another.
The %{name}-devel package contains header files for developing
applications that use %{name} to communicate with ActiveMQ brokers.
%{name}-devel contains development header files.
# %package doc
# Summary: C++ implementation header files for JMS-like messaging
# Group: Documentation for the CMS API
# %if %{?fedora}%{!?fedora:0} >= 10 || %{?rhel}%{!?rhel:0} >= 6
# BuildArch: noarch
# %endif
#
# %description doc
# activemq-cpp is a JMS-like API for C++ for interfacing with Message
# Brokers such as Apache ActiveMQ. C++ messaging service helps to make
# your C++ client code much neater and easier to follow. To get a better
# feel for CMS try the API Reference. ActiveMQ-CPP is a client only
# library, a message broker such as Apache ActiveMQ is still needed
# for your clients to communicate.
#
# %{name}-doc contains api documentation.
#
%prep
%setup -q -n activemq-cpp-library-%{version}
%build
./autogen.sh
# Build pdf(30MB) rather than default html(400MB).
%configure --disable-static --disable-doxygen-html --disable-doxygen-pdf
make %{?_smp_mflags}
#make %{?_smp_mflags} doxygen-run
#make %{?_smp_mflags} doxygen-pdf
%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -name '*.la' -exec rm -f {} ';'
rm $RPM_BUILD_ROOT/%{_bindir}/example
%clean
rm -rf $RPM_BUILD_ROOT
%check
make %{?_smp_mflags} check
%post -p /sbin/ldconfig
%postun -p /sbin/ldconfig
%files
%defattr(-,root,root,-)
%{_libdir}/lib%{name}.so.*
# %doc LICENSE.txt NOTICE.txt README.txt RELEASE_NOTES.txt
%files devel
%defattr(-,root,root,-)
%{_libdir}/lib%{name}.so
%{_includedir}/%{name}-%{version}
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/activemqcpp-config
# %files doc
# %defattr(-,root,root,-)
# %doc doc/%{name}.pdf
%changelog
* Wed May 05 2015 Israel Shirk <[email protected]> - 3.8.2
- Updated somewhat, runs on RHEL 6... Removed docs due to dependency hell
* Wed Sep 08 2010 Tim Bish <[email protected]> - 3.2.3
- Create a new Spec by porting the Fedora Version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment