Re: WxPython For Python 3.5.1

On 29.02.2016 21:00, Robin Dunn wrote:
> Regardless, the current Phoenix master and the linked wxWidgets 
> submodule should work fine for building for Python 3.5 without needing 
> any extra files or tweaks.  Using Phoenix's build.py should take care 
> of the rest. If it doesn't please let me know what is missing
I've just tested the current Git master.
On non-english installations the build with Visual Studio 2015 may fail 
due to non-ASCII output of cl.exe:

ERROR: failed building wxWidgets
Traceback (most recent call last):
   File "build.py", line 1141, in cmd_build_wx
     wxbuild.main(wxDir(), build_options)
   File "D:\Python\Sources35\Phoenix\buildtools\build_wxwidgets.py", 
line 439, in main
     args.append("COMPILER_VERSION=%s" % getVisCVersion())
   File "D:\Python\Sources35\Phoenix\buildtools\build_wxwidgets.py", 
line 67, in getVisCVersion
     text = getoutput("cl.exe")
   File "D:\Python\Sources35\Phoenix\buildtools\build_wxwidgets.py", 
line 163, in getoutput
     output = output.decode('utf-8')  # TODO: is utf-8 okay here?
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 62: 
invalid start byte

The command line and output of cl.exe look like that for me:
     "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe"
     Microsoft (R) C/C++-Optimierungscompiler Version 19.00.23026 für x86


Please apply the encoding modification from config.py also to 
build_wxwidgets.py.
But still the build may fail if the codepage is not 1252. Maybe build.py 
should call "chcp 1252" or this should be added to the build instructions.
(The use of code page 1252 was recommended by the waf people when I 
first ran into encoding problems.)


Regards,

Dietmar

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.