How to detect if the crypto++ package is installed on a particular system?

[Craig Sanders]

Hello all.

Does anyone one know if any methods/utilities exist to detect if the
crypto++ package is installed on a particular system? The reason that
I ask is because I am looking at incorporating the crypto++ package
into an Open Source Unix/Linux based project that I am working on.
This Open Source project makes use of the GNU Autotools, i.e.
Autoconf, Automake, Libtool, et al., which in turn means that any
potential future users of my project should be able to configure,
build, and install it (assuming that the packages/libraries upon which
it depends are correctly installed) by issuing the following command
from the Unix/Linux command line ;

> configure && make && make install.

The trouble is, I don't know of any ways that currently exist, to get
my configure script to detect if the crypto++ package is installed on
a system. I have searched through the Autoconf archives (located at
http://autoconf-archive.cryp.to/) and on Google, but it appears that
no one has written anything that does what I need to do.

Therefore I decided to write my own Autoconf macro to detect if the
crypto++ package is installed on a system. It is based to a large
extent on the Autoconf macro which detects if the Boost C++ libraries
are installed on a system. Hence, I was wondering if this macro would
be useful to the wider crypto++ community and if I should upload it to
the Autoconf archive, or does something like this already exist and I
am just not aware of it?

Furthermore, I have also written some files which allow the crypto++
package to be packaged up as a GNU Autotools project. This means that
the crypto++ package can also be configured, built, and installed on
Unix/Linux systems using the 3-part command that I listed above. So
far however, I have only tested it on my ix86/Linux machine. I haven't
tested it on my sparc/Solaris machine or my HP-UX machine as yet. I am
wondering if these files would also be useful to the wider crypto++
community, and if so, what I should do with them?

Thanks for any help and have a great day.


- Craig Sanders

[zooko]

Dear Craig Sanders:

I would be quite interested in your autoconf/autotools work on Crypto+
+. I don't have commit authority to the Crypto++ source code
repository though -- as far as I know only Wei Dai does. (Does
anyone else?)

Could you please post your patches to this list?

Thanks!

Regards,

Zooko

[Jens Peter Secher]

2008/7/24 Craig Sanders <rabbitl...@gmail.com>:
>
> [ Macros for autoconf detection of crypto++ ]

> Hence, I was wondering if this macro would
> be useful to the wider crypto++ community and if I should upload it to
> the Autoconf archive, or does something like this already exist and I
> am just not aware of it?

I am not aware of any such macros, so please also post it here. I
could then also include it in the Debian package if it is alright with
you.

>
> Furthermore, I have also written some files which allow the crypto++
> package to be packaged up as a GNU Autotools project.

I have previously written such files (configure.ac and Makefile.am)
for the Debian package. Have you seen those?

Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?

[Craig Sanders]

Hello Jens.

Thankyou for your response to my query. My apologies for having taken
so long to respond to it - I only noticed your message in my gmail
Inbox 2 days ago.

I have temporarily put the development of my Autoconf cryptopp
detection macro on hold whilst I have been trying to package up the
cryptopp package to make use of the GNU Autotools. However, now that I
have read through your message, it seems that you have already beat me
to this task. Therefore, I would be extremely interested in having a
look at the configure.ac and Makefile.am files that you have written
if that is okay with you, since I haven't seen them. Would you please
be able to e-mail them directly to me or provide me with the URL of
where I can find them?

With regard to the GNU Autotools based cryptopp package that I have
been working on, I am able to get it to successfully configure, build
and install on an x86 machine running Linux (Fedora Core 2) as well as
a Sun Sparc-II machine running Sun Solaris. These machines are using
the GNU g++ compiler versions 3.3.3 and 3.4.x respectively. I have
also tried my package on an old version of SuSE Linux (g++ version
2.95.3) but I got a slew of Compiler errors when I attempted to build
it.

Once I get my Autoconf detection macro finished you are welcome to use
it in the Debian packages. I also intend to contribute it to the
Autoconf macro archive for the wider Autotools community to use.

Thanks once again and have a great day.


- Craig Sanders

On Jul 31, 8:18 pm, "Jens Peter Secher" <j...@debian.org> wrote:
> 2008/7/24 Craig Sanders <rabbitlover2...@gmail.com>:

[Jens Peter Secher]

2008/8/8 Craig Sanders <rabbitl...@gmail.com>:

>
> if that is okay with you, since I haven't seen them. Would you please
> be able to e-mail them directly to me or provide me with the URL of
> where I can find them?
>

Sure, they are in
http://ftp.de.debian.org/debian/pool/main/libc/libcrypto++/libcrypto++_5.5.2-2.diff.gz.
See debian/rules for how they are used.
The Debian package builds on these architectures:
http://people.debian.org/~igloo/status.php?packages=libcrypto%2B%2B.

>
> Once I get my Autoconf detection macro finished you are welcome to use
> it in the Debian packages. I also intend to contribute it to the
> Autoconf macro archive for the wider Autotools community to use.
>

Great.