From: Ross M. <it...@cr...> - 2007-04-11 08:20:55
|
Hi, I've read a few posts about this already on the mailing list but nothing conclusive. Could somebody confirm for me: 1) Is it simply a case of getting someone to compile the current development code or is extra work needed on the codebase? 2) Is there a roadmap or commitment from anyone for releasing a win32 package in the future? I am curious as I have a win32/2.5 based app that could really do with some ldap functionality and if I can get the current status of project then I'll be in a better position to help... -ross |
From: <mi...@st...> - 2007-04-11 08:27:48
|
Ross, Ross McKerchar wrote: > > 1) Is it simply a case of getting someone to compile the current > development code or is extra work needed on the codebase? There should not be any effort needed on the codebase. > 2) Is there a roadmap or commitment from anyone for releasing a win32 > package in the future? Some people did Win32 builds before. But they did not keep up with Python and python-ldap development. And the builds did not support SASL functionality. > I am curious as I have a win32/2.5 based app that could really do with > some ldap functionality and if I can get the current status of project > then I'll be in a better position to help... Your help would be appreciated. Probably using MingW? Ciao, Michael. |
From: Ross M. <it...@cr...> - 2007-04-11 09:37:20
|
Michael Ströder wrote: >> I am curious as I have a win32/2.5 based app that could really do with >> some ldap functionality and if I can get the current status of project >> then I'll be in a better position to help... > > Your help would be appreciated. Probably using MingW? Hi Michael, I've just been investigating this and, although I'm not a complete stranger to building with MingW, my initial findings are that I'm a bit out of my depth. Statements like 'Cyrus SASL on Windows is still laregely a "work in progress"' and Jonathan Bowman's experiences (http://sourceforge.net/mailarchive/message.php?msg_name=7a2b5dfb0702100528t64cfeaf0gd7859338f998a0d0%40mail.gmail.com) suggest that I am very unlikely to succesfully navigate my with through such unfamiliar territory in a reasonable time-frame. I am, however, in a position to offer a donation to the project, if that would allow someone with more experience than me to complete the build (any takers?). Alternatively I am willing to be persuaded that the DIY option isn't as tricky as appears, so if someone is willing to offer me some extended pointers they would be greatly appreciated. -ross |
From: Mauro C. <mci...@li...> - 2007-04-16 17:18:41
|
Ross McKerchar wrote: > Statements like 'Cyrus SASL on Windows is still laregely a "work in progress"' and Jonathan Bowman's experiences (http://sourceforge.net/mailarchive/message.php?msg_name=7a2b5dfb0702100528t64cfeaf0gd7859338f998a0d0%40mail.gmail.com) > suggest that I am very unlikely to succesfully navigate my with through such unfamiliar territory in a reasonable time-frame. > I have built Python-LDAP on Windows in the past, and this should just mean that you'd have to exclude SASL from the targets, i.e. no support for SASL on Windows (just as Michael correctly pointed out). How unfortunate this could be in your situation, I don't know. > Alternatively I am willing to be persuaded that the DIY option isn't as tricky as appears, so if someone is willing to offer me some extended pointers they would be greatly appreciated. It isn't _really_ tricky, at least not as tricky as it used to be when OpenLDAP didn't support Windows natively. Now it's just a matter of downloading the sources (Python, OpenLDAP, OpenSSL, BDB, Python-LDAP), setting up your MinGW build environment, and launching "make" (wait a while). Note that you don't need to build Python, nor BDB, but you'll need some headers; and you'll only need shared libraries, headers and libs from OpenLDAP and OpenSSL, not the whole OpenLDAP thing (most of all not slurpd, which did not build at all on my Windows box last time). The whole activity does take a while, though, last time I could afford the time I used a couple days interspersed in a week of real work. HTH Mauro |
From: <mi...@st...> - 2007-04-11 11:04:47
|
Ross McKerchar wrote: > Michael Ströder wrote: >>> I am curious as I have a win32/2.5 based app that could really do >>> with some ldap functionality and if I can get the current status of >>> project then I'll be in a better position to help... >> >> Your help would be appreciated. Probably using MingW? > > I've just been investigating this and, although I'm not a complete > stranger to building with MingW, my initial findings are that I'm a bit > out of my depth. Statements like 'Cyrus SASL on Windows is still > laregely a "work in progress"' You'd probably should start asking on openldap-software mailing list how to build OpenLDAP client libs and all required libs for Win32 with MingW (MSYS). Symas is doing this. Rich Megginson wrote this: http://wiki.mozilla.org/LDAP_C_SDK_SASL_Windows See also current related discussion in news:mozilla.dev.tech.ldap Ciao, Michael. |
From: David L. <d...@ad...> - 2007-04-11 11:44:25
|
it might be possible to modify python-ldap to work with wldap32.dll and avoid openldap on win32. (see 'references' at http://msdn2.microsoft.com/en-us/library/aa367008.aspx) mingw comes with a winldap.h, but I don't know how close it is to the one that comes from the official platform sdk headers. python's distutils supports mingw, so this path looks quite attractive. d Michael Ströder wrote: > Ross McKerchar wrote: > >> Michael Ströder wrote: >> >>>> I am curious as I have a win32/2.5 based app that could really do >>>> with some ldap functionality and if I can get the current status of >>>> project then I'll be in a better position to help... >>>> >>> Your help would be appreciated. Probably using MingW? >>> >> I've just been investigating this and, although I'm not a complete >> stranger to building with MingW, my initial findings are that I'm a bit >> out of my depth. Statements like 'Cyrus SASL on Windows is still >> laregely a "work in progress"' >> > > You'd probably should start asking on openldap-software mailing list how > to build OpenLDAP client libs and all required libs for Win32 with MingW > (MSYS). Symas is doing this. > > Rich Megginson wrote this: > http://wiki.mozilla.org/LDAP_C_SDK_SASL_Windows > > See also current related discussion in news:mozilla.dev.tech.ldap > > Ciao, Michael. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > -- David Leonard d...@ad... Ph:+61 404 844 850 |
From: <mi...@st...> - 2007-04-12 12:02:00
|
David Leonard wrote: > it might be possible to modify python-ldap to work with wldap32.dll and > avoid openldap on win32. We had a thread on this list with subject "winldap?" back in 12/2006. My main concern is who is going to provide *continous* support for this? Personally I can't. Also I suspect that different versions of wldap32.dll have different feature sets. I don't have enough knowledge about that. > python's distutils supports mingw, so this path looks quite attractive. I don't want to hold anybody back, but I'd like to remind everybody hacking in this direction to think about who is going to maintain this code for the next two years or so. I'd suggest to create a completely separate C module called _winldap for that purpose. And given that we e.g. added support for OpenLDAP's ldap_str2dn() the gap between OpenLDAP libs and other vendor's LDAP libs gets bigger. And how about extended controls? Ciao, Michael. |