[20177] in Kerberos_V5_Development
Re: Building the PKINIT plugin on Windows
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Oct 9 13:01:17 2020
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <7eab5731-477e-212c-4418-80e0d3394700@mit.edu>
Date: Fri, 9 Oct 2020 13:00:53 -0400
MIME-Version: 1.0
In-Reply-To: <202010091539.099FdWLH028459@hedwig.cmf.nrl.navy.mil>
Content-Language: en-US
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 10/9/20 11:39 AM, Ken Hornstein wrote:
> I guess I'm wondering exactly what kind of infrastructure you want
> in the Windows build process; do you want to have it build OpenSSL
> as well, or simply point to already-built OpenSSL libraries?
Either is okay, but:
1. We need to be able to document (in src/windows/README) any necessary
setup for the development environment,
2. When we build the MSI installer, we presumably need to include
OpenSSL DLLs, but don't want to conflict with other packages which might
also depend on OpenSSL, and
3. I don't want to check OpenSSL sources or binaries into the krb5
repository.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
