Nice job on the blog! When i checked out the latest version of
heekspython, i couldn't get it to work. Crashes all over the place. I
really need to work on this dependency repository thing. Anyways, on a
philosophical note. I don't like this #undef _DEBUG stuff. For various
reasons, it isn't possible to build a debug wxpython without using a
debug python. And you can't build a release wxpython with a debug
wxwidgets. I think debug everything is really useful and there should
be a reasonable way for developers to take advantage.
I've made some changes to the codebase and am tempted to check it all
in. Erasing the #undef _DEBUG, but I wanted to see what other people
thought first.
Here's a little outline of how i got it to build what i think is the
right way. I'll get this on the wiki soon.
Download python source to your hard disk. I got version 2.6.2?
Open the visual studio solution file in pythondir\PCBuild and let it
do its conversion.
Select configuration debug and hit build. This will run for a while,
and then will complain about ~7 build failures, don't worry about
these.
Select configuration release and hit build as well.
Download wxpython sources to your hard disk and unpack
This one is tricky because if you mess anything up, you'll have to
delete the entire tree, unpack and start over
rename the file in wxpythondir\include\wx\msw\setup0.h to setup.h
edit this file and change the following lines
wxUSE_GRAPHICS_CONTEXT 1
wxUSE_GLCANVAS 1
wxUSE_POSTSCRIPT 1
wxUSE_DATEPICKCTRL_GENERIC 1
open up your visual studio command prompt and cd to
wxpythondir\build\msw
then type
nmake -f
makefile.vc SHARED=1 MONOLITHIC=0 USE_OPENGL=1 USE_GDIPLUS=1
UNICODE=1 BUILD=debug
this will run for a while and hopefully not say anything bad
then cd to wxpythondir\contrib\build\stc
nmake -f
makefile.vc SHARED=1 MONOLITHIC=0 USE_OPENGL=1 USE_GDIPLUS=1
UNICODE=1 BUILD=debug
then cd to wxpythondir\contrib\build\gizmos and issue a
nmake -f
makefile.vc SHARED=1 MONOLITHIC=0 USE_OPENGL=1 USE_GDIPLUS=1
UNICODE=1 BUILD=debug
then cd to
wxdir\wxpython
and type
pythondir\PCBuild\python_d.exe setup.py build_ext --inplace
MONOLITHIC=0 --debug
then all should be well. the original visual studio project at least
describes what relative directories you need to use for linking and
including. The dll's must get copied to the heekscad directory.
Heekscad then needs to be changed to link against the wxwidgets libs
produced through this process. It is important to note that wxpython
source includes the wxwidgets source and this process builds them
both. You can't use different build of wxwidgets in different parts of
the program.