[issue1249] build compatibility

[Patrick Waugh]

New submission from Patrick Waugh <ptwaugh at gmail.com>:

Just FYI, as Python was build with VS 2003, those of us with more modern 
systems (like VS 2008) get the following when we try to build mercurial:

C:\bin\mercurial\mercurial-1.0.1                                               
> python setup.py build                                                        
running build                                                                  
running build_py                                                               
running build_ext                                                              
error: Python was built with Visual Studio 2003;                               
extensions must be built with a compiler than can generate compatible binaries.
Visual Studio 2003 was not found on this system. If you have Cygwin installed, 
you can try compiling with MingW32, by passing "-c mingw32" to setup.py.       
                                                                               
C:\bin\mercurial\mercurial-1.0.1                                               
>                                                                              

If you guys are going to post a build method, don't you think it should 
actually work with current tools?   I mean, no real programming shop is using 
a 5 year old tool!

----------
messages: 6653
nosy: pwaugh
priority: urgent
status: unread
title: build compatibility

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1249>
____________________________________________________