[Chandler-dev] wx merges: how-to and current status
robin at alldunn.com
Mon Mar 3 13:22:01 PST 2008
Since my contract is now over I thought it would be a good idea to make
sure there is a record of how I've been doing the merges from upstream
wxWidgets into the wx that OSAF uses so somebody else would be able to
do it if needed. I wrote up the instructions for how to do it about a
year and a half ago and have been following those directions since then.
The instructions are in the OSAF wx SVN repository and can be seen at
Current status: I did a merge last week using the then current wx
sources from the WX_2_8_BRANCH, but I didn't roll it over to chandler
because I was getting some seemingly random errors when running the
functional tests. (One of the recorded scripts would fail sometimes on
Windows, and would succeed sometimes.) This may not be a real problem
however because over the weekend I backed out to the older wx and there
were still some functional test failures for me there too. Anyway, the
status of the current merge is that it has been done up to step 13 in
the instructions so if you decide to go with it you just need to make
the change in external/wx/Makefile and then in chandler/Makefile once
the tboxes have built the binary tarballs.
I'm still keeping some of the wx specific Chandler bugs in mind and will
work on them when I can. If solutions are found and fixed upstream I'll
let you know.
http://wxPython.org Java give you jitters? Relax with wxPython!
More information about the chandler-dev