[2189] in Kerberos_V5_Development
Re: Comments on Krb5-nt-alpha1 - Using Borland C++
daemon@ATHENA.MIT.EDU (Doug Engert)
Mon Jan 27 16:02:09 1997
Date: Mon, 27 Jan 1997 15:00:10 -0600
From: Doug Engert <DEEngert@anl.gov>
To: Sean Moore <sean.moore@raleigh.hcl.com>
Cc: krbdev@MIT.EDU, deengert@anl.gov
In-Reply-To: <3.0.32.19970127152929.0094b100@nfs1>
Sean Moore writes:
> At 08:29 PM 1/25/97 -0500, Doug Engert wrote:
>
> > (1) I was unable to use the krb5_32.lib which was created
> > by the make. But I was able to create a new
> > krb5_32.lib which the Borland C++ 4.51 linker
> > could use. This was done using the krb5_32.def file
> > as input to the Borland implib command.
>
> No def file is needed just use implib with any dll as
> an argument.
That is what I tried first, but implib crashed when I tried using
the krb5_32.dll. But using the krb5_32.def file worked.
>
> > (2) I Had to add defines for:
> > KRB5_DLLIMP=
> > KRB5_CALLCONV=__stdcall
> > KRB5_CALLCONV_C=__cdecl
> >
> > The defines were needed since the __declspec(dllimport)
> > is a Microsodt specific extention to the language. By defining
> > the above, this circumvented the definition of these in win-mac.h
> > when the krb5.h file is included in the application.
>
> Yes __declspec(dllimport) is MS specific but please dont
> take it out because it is a speed enhancment for apps
> but just check for
> #ifdef _MSC_VER
I will try this tonight. I am content to built the Krb5 distribution
with the Microsoft compiler. But I have built the application with
Borland C++ using OWL and it would not be an easy conversion.
>
> >I am not sure if the above two problems are related, but
> >please reconsider the use of __declspec(...) at least when
> >used outside the DLL.
>
> The two are unrelated because any *.lib you make with one
> compiler is not going to useable by the other.
>
> sean
Thanks for the comments.
--
Douglas E. Engert <DEEngert@anl.gov>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
