Re: Win32 Binaries?

[Mauro C. <mci...@si...>]

Michael Str=F6der wrote:

> >BTW Michael, how would you let the different setp.cfg versions co-exis=
t?
> I think Build/ is the right place.=20

Right. I'd create a "Build/win32" dir and put the setup.cfg there.=20
Obviously the main dir should have pointers to let people know they=20
should look into "Build/<platform>".

> We should stick with one way which is DistUtils.

OK. I guess you can zap directory "Win32" from the CVS tree altogether,=20
then.

>> I did have to extend setup.py a bit; I attach the unified diff here.
>
> Hmm, can web apply changes one-by-one? I'd really like to see in the=20
> diff what was changed.

Right. I attach a file where I try to let changes stand out more.
The changes I had to insert are:
1. I needed extra options for the linker; so I added "extra_link_args"=20
to the class definition and passed it to the constructor.
2. I hijacked the "data files" mechanism in Distutils to carry over the=20
Cyrus-SASL DLL. I added "extra_files" to the class definition and passed =

it to setup() as the "data_files" param. I also had to add a loop to=20
process that setting in the setup.cfg.
3. I added the library names I got under Win32 for LDAP (oldap_r) and=20
SASL (libsasl) to the macro-definition logic.

> ... avoid DistUtils warning messages. Unfortunately this doesn't work=20
> with Python versions prior 2.3.
>
> error: build_py: supplying both 'packages' and 'py_modules' options is =

> not allowed=20

Hmmm, this is unfortunate. I wasn't aware of this limitation. I wonder wh=
y?
If so, let's revert to the old style. However, there's one file missing=20
from the manually-built list (ldap/filter.py). Is this intentional?

> Which version of Cyrus SASL?

I got it from their CVS a few days ago; so it must be later than 2.1.2=20
which is the latest source tarball available on their site.
I didn't use 2.1.2 because it has serious problems building on Windows,=20
whereas the CVS version builds like a charm out of the box.

> Is the name 'libsasl' also version dependent like on Linux/Unices=20
> (sasl vs. sasl2)?

It appears not to; in fact, the MSVC project files included with the=20
sources build a DLL called LIBSASL without any indication of the version.=


> Could you please send it to me personally? I will make it available as =

> public download with experimental status.=20

Done. You'll get it in a separate message ;-)

Mauro