[19972] in Kerberos_V5_Development
Re: Building static libraries on Windows
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Sep 18 13:38:05 2019
To: Sandeep Patil <sandpa@gmail.com>, <krbdev@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <e8df804d-34cc-fbe7-46c7-91495ffd286a@mit.edu>
Date: Wed, 18 Sep 2019 13:37:28 -0400
MIME-Version: 1.0
In-Reply-To: <CAAMh-L4wT5J6Z30tpTU5a=SdRFoRkyQmduM3gnuB-u97tD4KLg@mail.gmail.com>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
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
