Hi,
On 6 July 2012 21:58, OlyDLG wrote:
> Yes, but many 32-bit apps still run on 64-bit, so I figured it was worth a
> try; I forgot that the win32 probably (necessarily?) implied that the Python
> it would need to run against would also have to be 32-bit.
>
> As far as my alternatives at this point: advice from CB notwithstanding, I'd
> like to give the latter a try; if I download the source, I don't suppose it
> comes w/ a setup.py? If not, what's the approach? A Visual Studio Project?
> Thanks!
This is what I did (based on Robin's recommendations):
1) Got the wxWidgets sources from SVN;
2) Got the Phoenix sources from SVN;
3) Installed cygwin;
4) Installed Visual Studio 2008;
Then followed Robin's advice, quoted below:
"""
I think you should probably already have everything else that you need
since you are able run the etg scripts and build the docs. The
build.py tool will download a sip binary (and will also update it when
I switch to new versions) so if you also have Visual Studio 2008 then
I think you should be good to go. Just make sure that the cl.exe
executable is on the PATH and that the link.exe found first on the
PATH is the one from VisualStudio and not the one from cygwin. I
don't remember for sure but some of the command line tools like nmake
may be an optional part of the install for Visual Studio, so you may
want to double check that.
Currently the "build" command in build.py will run both the build_wx
command (which builds wx widgets) and the setup_py command (which will
build Phoenix using setup.py.) There is also a new build command
available for building Phoenix called "waf_py" which uses the waf tool
instead of setup.py. It doesn't support installs yet which is why I
haven't switched it to be the default, but since you can run in-place
after the build using the Phoenix/wx dir as your wx package there
hasn't been a strong need for duplicating install and other distutils
commands yet. Anyway, building with waf is lots faster[1] because it
can do parallel builds (build.py defaults to 1 build job per processor
core) and it will do better dependency checking and skip recompiling
files that don't need to be rebuilt. Build.py will download a copy of
waf automatically if you run this command so you don't need to worry
about installing anything and keeping it up to date, just like the sip
binary. To use it use the "build_wx waf_py" commands with build.py
instead of just "build".