This page was for tracking transitioning packages from wxwidgets2.8 to wxwidgets3.0 and wxpython3.0. The transition is now complete, but the summary information has been left in case it is still of interest.
Jessie released with wxWidgets 3.0.2 and wxPython 188.8.131.52 (wxPython 184.108.40.206 was too late for the freeze).
There's a backported version on wxWidgets 3.0.x in wheezy-backports, and a backport of wxPython 3.0.x is planned).
The wxwidgets2.8 packages did not release with jessie, and were removed from unstable in January 2016.
For C++ packages, the package you probably want to build-depend on is libwxgtk3.0-dev (or if you only use the 'wxbase' library, libwxbase3.0-dev). There's no need to also build-depend on wx3.0-headers or wx-common, and there's no need to build-depend on both libwxgtk3.0-dev and libwxbase3.0-dev.
Some important notes:
- There may be overlaps with other on-going transitions. Please check for this, and delay uploads of affected packages until after these transitions have been completed.
- You can co-install wx 2.8 and 3.0, so applications can switch independently of one another.
- The wxwidgets2.8 source package was actually based on wxPython (which includes an embedded copy of the C++ wxWidgets library sources), but the wxwidgets3.0 source package is just the C++ library (one motivation for this change was that wxPython 220.127.116.11 appeared some time after wxWidgets 3.0.0).
- Upstream now defaults to enabling their "WXDEBUG" checks for incorrect API usage. One consequence of this is that in 2.8, the -dbg packages were a version built with these checks on, and debug info, but in 3.0, the -dbg packages are just detached debug symbols. The other is that code which misuses the wx API may now pop up warning dialogs, while previously the code would have quietly muddled through. Overall sorting out such issues is good, but these dialogs are intrusive for users. Where upstream hasn't tried wx 2.9.x or 3.0, this means that even if you get a clean build, the result may not be usable, so testing as much functionality of the rebuilt package as you can is important. These assertions can be disabled by defined NDEBUG when building the application - e.g. by adding -DNDEBUG to CPPFLAGS, which means such assertions will be handled as they would have been by a default build of 2.8 (such as that in wxgtk2.8-0).
- The wx3.0-doc package was temporarily gone in the version released with jessie, due to changes in how upstream generated this documentation - it was reinstated in wxwidgets3.0 3.0.2-2.
Upstream provide a document listing "Changes Since wxWidgets 2.8", which may be useful where the upstream code needs updating. The other common build failures are due to compatibility with wx2.6 being off in the 3.0 packages (which is upstream's default).
Popcon graph showing installs of the wx3.0 runtime library and wxpython 3.0 packages:
Popcon graph showing installations of wx C++ and Python runtimes for wx 2.6, 2.8 and 3.0: