On 27.11.2009 23:08, Sune Foldager wrote:
> Adrian Buehlmann wrote:
>>> Now I'm curious if Python will use (or can be made to use) these
>>> compilers to build C extensions.  Perhaps we can drop mingw entirely.
>>>
>> Indeed. The compiler in Windows 7 SDK seems to be the full
>> optimizing C++ compiler. I doubt there is any difference to the
>> one shipping with Visual C++ (modulo libraries like MFC and
>> ATL of course, which hopefully no one is using for these kind
>> of things).
> 
> Why does this matter, though? I always use binary installers for python
> and that works fine. Why would we need to build it from scratch? We
> (Edlund) use 2.6 since it's built with 2008, so I guess we (TortoiseHg)
> would do the same, or rather the 7.0 SDK which should be the same.

I think Steve was talking about compiling the C extensions for
Python of Mercurial (= Mercurial source files written ins C).

And I was trying to emphasize that ATL is probably not part
of the Windows 7 SDK suite (CuteHg used ATL in the beginning, IIRC).


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop

Reply via email to