[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Crypto] Native BC build
From: |
Raif S. Naffah |
Subject: |
Re: [GNU Crypto] Native BC build |
Date: |
Wed, 20 Nov 2002 22:57:19 +1100 |
User-agent: |
KMail/1.4.3 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
On Sunday 17 November 2002 09:57, Casey Marshall wrote:
> I've put together a repackaged version of the BouncyCastle JCE
> library, with the supporting files necessary for building this as a
> shared relocatable library, which can then be used to build all of
> GNU Crypto with GCJ.
>
> It should be as simple as `./configure; make; make install':
>
> http://metastatic.org/src/jce-1.15.tar.gz
>
> The attached patch modifies gcj/configure.in and
> gcj/source/Makefile.am to optionally build the JCE adapter classes
> when the configure option --with-jce-jar. I didn't check this in yet
> since I'd like someone else to
i tested gnu-crypto with the above JCE implementation and all works
fine!
i checked in the patch. for the time being:
a. you need to run ./admin.sh conf (or the auto* trilogy), in the gcj/
directory, and
b. add $(path-to-installed-jce-lib) to your $LD_LIBRARY_PATH before
making the shared reloadable gnu-crypto.
> I'm also still of the opinion that the CVS sources should not contain
> Makefile.in's or configure's. These are fine for releases, but I
> think if someone is hacker enough to check out CVS, they should be
> able to figure out the extra steps.
yes i agree with you. how about only generating and bundling them in
the deliverables when we make a distribution?
thanks for taking the time to put together the BC code :-)
cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique
iD8DBQE923ig+e1AKnsTRiERA465AJ980UrTIY9GE7phS4jENFcP3BQ1VACg/w5O
a2Zy4lI7/gLdGtZJEHSrhxw=
=715s
-----END PGP SIGNATURE-----