Hello,
My PC has installed both VC9 and VC10.
When I compile 2.9 with the command "python build-wxpython --
build_dir=../bld", I found that when this work was starting up, it
called VC10, but when linking, it called VC9.
When I set up the PYTHONPATH, tried to launch the demo/demo.py, it
showed a "Fatal Error" about different libraries. So how should I
compile wxPython by VC10 forcibly ? Thanks !
All I've ever had to do in the past is to ensure that the desired version of MSVC is found first in the PATH, however I think that starting with about Python 2.6 distutils is now checking the registry for the location of the compiler and tools that it wants to use. Take a look at the distutils.msvc9compiler to check that and to see exactly what it is doing.
That said, unless you are also rebuilding Python itself with VC10, and also *all* extension modules that you are using, then you do not want to build wx and wxPython with it. Stick with VC9 in that case.
On 9/18/11 8:54 PM, Bo Zhou wrote:
Hello,
My PC has installed both VC9 and VC10.
When I compile 2.9 with the command "python build-wxpython --
build_dir=../bld", I found that when this work was starting up, it
called VC10, but when linking, it called VC9.When I set up the PYTHONPATH, tried to launch the demo/demo.py, it
showed a "Fatal Error" about different libraries. So how should I
compile wxPython by VC10 forcibly ? Thanks !
--
Robin Dunn
Software Craftsman