Re: Phoenix: Issues encountered doing a Windows build from a git clone

Const <[email protected]>
Newsgroups gmane.comp.python.wxpython.devel
Message-ID <[email protected]>
On Tuesday, April 28, 2015 at 11:28:24 AM UTC-2:30, Const wrote:
>
> These are the errors encountered on a Windows 7 machine when trying to 
> build Phoenix from a fresh clone.  Solutions are provided too.
>
> The first is raised by "build.py dox":
>
>     Running command: dox
>     Checking for 
> C:\Users\Const\Documents\GitHub\Phoenix\bin\doxygen-1.8.8-win32.exe...
>     Not found.  Attempting to download...
>     Connection successful...
>     Data downloaded...
>     Checking for 
> C:\Users\Const\Documents\GitHub\Phoenix\bin\doxygen-1.8.8-win32.exe...
>     Command 'c:/cygwin/bin/cygpath -u C:/Users/Const.8.8-win32.exe' failed
>      with exit code 1.
>     The system cannot find the path specified.
>
> The fix is to install Cygwin.
>
> Now, run "build.py dox" again and you'll get:
>
>     Running command: dox
>     Checking for 
> C:\Users\Const\Documents\GitHub\Phoenix\bin\doxygen-1.8.8-win32.exe...
>     c:/cygwin/bin/bash.exe -l -c "cd C:/Users/Const && ./regen.sh xml"
>     ./regen.sh: line 15: $'\r': command not found
>     ./regen.sh: line 16: $'\r': command not found
>     : No such file or directoryregen.sh
>     ./regen.sh: line 72: syntax error near unexpected token `$'in\r''
>     '/regen.sh: line 72: `case "$1" in
>     Command 'c:/cygwin/bin/bash.exe -l -c "cd C:/Users/Const
>     && ./regen.sh xml"' failed with exit code 2.
>
>
> To fix, remove the "\r" from the regen.sh file (i.e. convert to Unix line 
> endings). regen.sh is in /ext/wxWindows/docs/doxygen.
>
> The next error is raised by "build.py etg": 
>
>     Running command: etg
>     "C:\Python34\python.exe" etg\_core.py --sip
>     ERROR: Graphviz command `dot` cannot be run (needed for Graphviz 
> output), check your ``PATH`` setting
>     Traceback (most recent call last):
>       File "etg\_core.py", line 469, in <module>
>         run()
>       File "etg\_core.py", line 462, in run
>         tools.runGenerators(module)
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\tweaker_tools.py", line 
> 577, in runGenerators
>         g.generate(module)
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\sphinx_generator.py", 
> line 2902, in generate
>         self.generateModule(module)
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\sphinx_generator.py", 
> line 2970, in generateModule
>         function(item)
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\sphinx_generator.py", 
> line 3066, in generatePyClass
>         docstring.Dump()
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\sphinx_generator.py", 
> line 2324, in Dump
>         return function(write)
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\etgtools\sphinx_generator.py", 
> line 2359, in DumpClass
>         png, map = inheritance_diagram.MakeInheritanceDiagram()
>       File 
> "C:\Users\Const\Documents\GitHub\Phoenix\sphinxtools\inheritance.py", line 
> 286, in MakeInheritanceDiag
>     ram
>         stdout, stderr = p.communicate(code)
>     UnboundLocalError: local variable 'p' referenced before assignment
>     Command '"C:\Python34\python.exe" etg\_core.py --sip' failed with exit 
> code 1.
>
> To fix, install Graphviz and put it on your PATH. Or use "build.py etg 
> --nodoc".
>
> Also, if you do a "build.py touch" you get:
>
>     Running command: touch
>     touch etg/*.py
>     'touch' is not recognized as an internal or external command,
>     operable program or batch file.
>     Command 'touch etg/*.py' failed with exit code 1.
>     Finished command: touch (0.20s)
>
> To fix, add touch.exe from uxnutils to your path, or make sure touch.exe 
> from Cygwin is on your path. 
>
> One final note: I have Visual Studio 2010 installed, which the build 
> script was able to find and use.  If the build script can't find 
> vcvarsall.bat, but you know where it is, you can run it manually from the 
> command prompt before running "build.py build".
>
>  
>
I should also make a comment about building a distribution. I wanted a 
wheel distribution, so my first naïve crack at it was "setup.py 
bdist_wheel". However, I got the following:
 
    running bdist_wheel
    running build
    WARNING: Building this way assumes that all generated files have been
    generated already.  If that is not the case then use build.py directly
    to generate the source and perform the build stage.  You can use
    --skip-build with the bdist_* or install commands to avoid this
    message and the wxWidgets and Phoenix build steps in the future.
    C:\Python34\python.exe -u build.py build
    Build using: "C:\Python34\python.exe"
    3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:44:40) [MSC v.1600 64 bit 
(AMD64)]
    Python's architecture is 64bit
    cfg.VERSION: 3.0.3
    Running command: build
    Running command: build_wx
    MSVC: c:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\BIN\amd64\cl.exe
    Traceback (most recent call last):
      File "build.py", line 1653, in <module>
        main(sys.argv[1:])
      File "build.py", line 170, in main
        function(options, args)
      File "build.py", line 1039, in cmd_build
        cmd_build_wx(options, args)
      File "build.py", line 1050, in cmd_build_wx
        checkCompiler()
      File "build.py", line 665, in checkCompiler
        os.environ['PATH'] = bytes(env['path'])
    TypeError: string argument without an encoding
    Finished command: build_wx (0.870s)
    Finished command: build (0.870s)
    Command 'C:\Python34\python.exe -u build.py build' failed with exit 
code 1.
 
Running "build.py bdist_wheel", however, worked. 
 

-- 
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.