[19973] in Kerberos_V5_Development
Re[2]: Building static libraries on Windows
daemon@ATHENA.MIT.EDU (Chris Hecker)
Wed Sep 18 16:57:51 2019
From: Chris Hecker <checker@d6.com>
To: Greg Hudson <ghudson@mit.edu>, Sandeep Patil <sandpa@gmail.com>,
<krbdev@mit.edu>
Date: Wed, 18 Sep 2019 20:57:42 +0000
Message-ID: <em9c3630f8-ee3b-48db-a2d5-f4a389b3d515@checker-t530>
In-Reply-To: <e8df804d-34cc-fbe7-46c7-91495ffd286a@mit.edu>
MIME-Version: 1.0
Reply-To: Chris Hecker <checker@d6.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
I build krb5 libs statically from source on windows, although I'm still
on an old version, but you can email me for my vcproj files and edits if
you want.
Chris
------ Original Message ------
From: "Greg Hudson" <ghudson@mit.edu>
To: "Sandeep Patil" <sandpa@gmail.com>; krbdev@mit.edu
Sent: 2019-09-18 10:37:28
Subject: Re: Building static libraries on Windows
>On 9/18/19 12:53 PM, Sandeep Patil wrote:
>> I want to link statically to the MIT Kerberos API on Windows. I am able to
>> build dlls using the instructions but cannot seem to find a way to specify
>> building of static libraries to the nmake build process (like you can do
>> with configure on Linux/Mac OS). Is there any way to do that ?
>
>As far as I know, the Windows build creates and installs .lib files
>(gssapi32.lib, krb5_32.lib, etc.) as well as DLLs.
>
>The regular build system does not actually support static libraries in a
>useful way. I added partial static build support to facilitate code
>coverage analysis for the test suite, but gcov has evolved to support
>dynamic libraries, so at some point I will probably remove support for
>--enable-static --disable-shared.
>_______________________________________________
>krbdev mailing list krbdev@mit.edu
>https://mailman.mit.edu/mailman/listinfo/krbdev
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
