gnu-crypto-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Crypto] Native BC build


From: Casey Marshall
Subject: Re: [GNU Crypto] Native BC build
Date: Wed, 20 Nov 2002 11:00:07 -0800
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Raif S. Naffah wrote:
> 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

That should have ended with "make sure it actually works". I'm not lazy,
just paranoid.

>
> 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.
>

Good. The `gcj/INSTALL' file should also have a blurb about how to build
the JCE stuff if desired, similar to the part about building the JUnit
tests.

>>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?
>

Yes, releases should build in the expected way (./configure; make; make
install); CVS (and pre-releases in general) is usually the "we're still
working on this" part.

>
> thanks for taking the time to put together the BC code :-)
>

- --
Casey Marshall < address@hidden > http://metastatic.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE929u2gAuWMgRGsWsRAkHMAJ9PBZQZOQyNYa5HLnbckij0wzrDoQCfahpr
SnJs1Rn1swjG7JmttEmVd2M=
=G1zz
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]