Dulwich C extensions and stand-alone Windows installation of bzr

[Alexander Belchenko]

Vincent Ladeuil пишет:
>>>>>> Alexander Belchenko <bialix at ukr.net> writes:
> 
>     > Eli Zaretskii пишет:
>     >>> Date: Fri, 09 Sep 2011 13:25:19 +0300
>     >>> From: Alexander Belchenko <bialix at ukr.net>
>     >>> CC: mbp at canonical.com, bazaar at lists.canonical.com
>     >>> 
>     >>> Python 2.6-2.7 are built with MSVC 2008 IIRC, so another version of
>     >>> run-time library should be used (msvcr90.dll IIRC).
>     >> 
>     >> Shouldn't be a problem, as MinGW comes with import libraries for
>     >> msvcr90.dll as well.  It's a matter of telling the right linker
>     >> switches in the appropriate README.
> 
>     > Python's distutils library can build C-extensions using mingw
>     > with appropriate switches. Maybe those switches could be
>     > extracted from some source, I can't say.
> 
> To refresh my dusted memory, I grepped the distutils dir for python2.7:
> 
>             """Python was built with Visual Studio 2008;
> extensions must be built with a compiler than can generate compatible binaries.
> Visual Studio 2008 was not found on this system. If you have Cygwin installed,
> you can try compiling with MingW32, by passing "-c mingw32" to setup.py.""")
> 
> The same warning exist for Visual Studio 2003.

Right.

> I also vaguely recall being able to put this flag into some dot file to
> avoid modifying the setup.py invocations (but it's so vague I wonder if
> it was for perl instead...).

You're talking about setup.cfg. But I never used it directly and have no 
idea about its syntax.

-- 
All the dude wanted was his rug back