adventures in debugging and the build

Windows XP

• sources: chandler-all
• tools required
  • visual studio
  • cygwin: gcc, gcc-g++
  • | make compilers | pulls mingw and puts it in external
• to build
  • | make expand build binaries install > log 2>&1 | from external
  • | make build binaries install > log 2>&1 | from internal
  • DEBUG=1 for debugging
  • you'll need the log file to diagnose problems
• wing ide to debug python (setup likely changes with new version of wing)
  • set python executable: chandler/release/bin/python.exe or chandler/debug/bin/python_d.exe
  • set PATH: chandler/release/bin or chandler/debug/bin
  • to use shell in wing, set PYTHONPATH: chandler
• visual studio solution file: internal/wxPython-2.5/build/msw/msw.sln
  • Tools/Debug processes...
  • run from wing, then attach to the process
• notes
  • gcc is used to build swig, afaik cl (msft compiler) is used for everything else
  • we build our own swig, without it pylucene, wxpython, m2crypto don't get wrapped
  • would be useful to have better feedback on whether or not each component of the build has succeeded or failed
  • would be nice to have a real sln file for wxWidgets
• Robin's wxPython debugging advice

other links:

• http://www.python.org/~jeremy/weblog/031003.html
• http://docs.python.org/lib/module-pdb.html

-- KatieCappsParlante - 28 Jul 2004