Compiling on windows

[Jonathan Bowman]

Yes, exactly. While we are at it, can we try to compile in sasl
support? The catch, so far, is, again, heimdal. It is not winsock
aware.

However, I have heard that it can be done. I am just stuck as to how.

Perhaps I should just ask a couple simple questions:

Should we use heimdal or MIT kerberos? I have been assuming heimdal,
as MIT kerberos does not compile with mingw/msys.

Should we use mingw/msys, or vc++? I have been assuming mingw/msys.

Is there a way to get mingw to use MIT kerberos libraries compiled with vc++?

If anyone can point me in the right direction, I would be grateful.

Thanks,
Jonathan Bowman

On 2/10/07, Anil Jangity <anilj at entic.net> wrote:
> There is a windows python-ldap (2.0.6 py 2.4) available here:
> http://www.agescibs.org/mauro/
>
> But its a little old...
>
> Anyone working on getting one up for python 2.5 and latest python-ldap release?
>
> On 2/10/07, Jonathan Bowman <bowmanj at users.sourceforge.net> wrote:
> > I have been trying to build python-ldap on Windows. First, I need to
> > build openldap on Windows using openssl, heimdal (kerberos 5, gssapi,
> > etc.), and cyrus-sasl. I am doing this using mingw (as I assume that
> > is what python-ldap uses).
> >
> > OpenSSL is not a problem, but then I get stuck on heimdal, which keeps
> > me from compiling cyrus-sasl. Should I be using MIT Kerberos instead?
> > (I do not know how to build MIT Kerberos using mingw). I am using
> > MSYS, heimdal has a problem with sockets on Windows.
> >
> > Can anyone give me any hints at all? At this point, I do not know how
> > to do this without getting involved in altering significant source
> > code in heimdal, which is beyond my means.
> >
> > Thanks for any response,
> > Jonathan Bowman
> >
> >