Testing both with OpenSSL and GnuTLS
Cesc Santa
cesc.santa at gmail.com
Wed Jun 27 22:06:19 CEST 2007
Hi,
Unless disk space is a problem ... checkout minisip head twice and have
separate compilation folders for each one (1 openssl, 1 gnutls) ...
Cesc
On 6/27/07, Mikael Magnusson <mikma264 at gmail.com> wrote:
>
> On Wed, Jun 27, 2007 at 09:44:00AM +0200, Mikael Svensson wrote:
> > Hello everybody
> >
> > For my thesis project I need to extract the SubjectInfoAccess extension
> > from X.509 certificates. As far as I can tell libmcrypto does not
> > support this functionality yet, so I am planning on adding
> > certificate::get_subjectinfoaccess() for this purpose.
> >
> > The problem is that the function must be developed both for OpenSSL and
> > for GNUTLS and I do not know how to do this.
> >
> > How do I first compile libmcrypto using OpenSSL, then test my code, then
> > recompile using GNU TLS and test my code one final time?
> >
>
> # Enable openssl and disable gnutls in build.d/build.local
> ./build.pl configure+compile libmcrypto
> # Test openssl
> # Enable gnutls and disable openssl in build.d/build.local
> ./build.pl configure+compile libmcrypto
> # Test gnutls
>
> > Is there a configure flag that forces linkage of OpenSSL or GNUTLS?
> >
>
> _______________________________________________
> Minisip-devel mailing list
> Minisip-devel at minisip.org
> http://lists.minisip.org/mailman/listinfo/minisip-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.minisip.org/pipermail/minisip-devel/attachments/20070627/265eb67c/attachment.htm
More information about the Minisip-devel
mailing list