Date: Fri, 10 Dec 2004 19:50:12 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-arch@freebsd.org Subject: Re: Adding standalone RSA code Message-ID: <20041211035012.GB93068@dragon.nuxi.com> In-Reply-To: <41BA6BDE.5070909@wadham.ox.ac.uk> References: <41B92CF3.2090302@wadham.ox.ac.uk> <20041211020518.GA74718@dragon.nuxi.com> <41BA6BDE.5070909@wadham.ox.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
[ #1, respect the reply-to ]
On Fri, Dec 10, 2004 at 07:39:10PM -0800, Colin Percival wrote:
> David O'Brien wrote:
> >At the moment, I think your library code should just be part of your
> >FreeBSD Update code if you find you simply cannot use OpenSSL. Or make
> >your library a port in which only a static library is provided.
>
> I'm not quite sure I understand what you're saying here.
In other words, rather than create an RSA library that your code links
against, just build .o's and list the .c's in your FreeBSD Update's
Makefile. That way you can use this RSA code that you want to, but it
isn't exposed as a consumable library in FreeBSD's {,/usr}/lib.
--
-- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041211035012.GB93068>