[Pidgin] #48: Make SIP/SIMPLE work with Microsoft Live Communication Server

[Pidgin]

#48: Make SIP/SIMPLE work with Microsoft Live Communication Server
---------------------------+------------------------------------------------
 Reporter:  MarkDoliner    |        Owner:  shulman
     Type:  patch          |       Status:  new    
Milestone:                 |    Component:  SIMPLE 
  Version:  2.0            |   Resolution:         
 Keywords:  MS LCS SIMPLE  |  
---------------------------+------------------------------------------------

Comment(by galiven):

 Replying to [comment:215 msalerno]:
 > Has anyone gotten this to build against mignw32?  I have been building
 the plugin on my linux server, and the latest release works great on OCS
 2007, but I would like to build a windows DLL to distribute for testing.
 I have been hacking away at the code to get it to compile in cygwin/mingw
 with some friends at work, but we have not had much luck.
 >
 > Any help would be appreciated.
 >
 > Thanks


 As you probably know, the problem is with Kerberos, on a standard
 Windows/Cygwin/MinGW environment, there is no krb5.h file to include or
 libraries to link against.  You can get
 [http://web.mit.edu/Kerberos/dist/#kfw-3.2 Kerberos for Windows], but even
 if you modify src/Makefile.mingw to try to include the kerberos headers
 and library, it fails.  From my research, it's starting to look like we
 would have to use Microsoft's implementation of Kerberos, which would
 basically mean another version of sipkrb5 for windows that used the
 Microsoft libraries described here: [http://msdn.microsoft.com/en-
 us/library/aa380496(VS.85).aspx].

 I've tried to get the source for MIT Kerberos to compile in the
 Cygwin/MinGW environment to no avail, they don't provide a mingw Makefile,
 and configure fails because cygwin doesn't provide resolv.h.  As a
 temporary measure, it could be possible to put #ifdef WIN32 around all the
 Kerberos stuff to disable Kerberos support on Windows to allow the plugin
 to compile like before, but this doesn't help the people that need
 Kerberos to connect to their OCS server (like me).

 Regarding the other recent discussions about getting development off this
 thread, I'm all for moving things to a forum topic on SIPE's already
 existing [https://sourceforge.net/forum/?group_id=194563 sourceforge
 page], I'd even be willing to set some things up, but when I previously
 asked fixxer to let me help with sourceforge my request was lost. . .  The
 only problem that I can see with sourceforge is that we would want to set
 up some sort of git-svn bridge so that the code could be viewed more
 easily from the sourceforge project.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/48#comment:247>
Pidgin <http://pidgin.im>
Pidgin