| | 1 | wxwidgets for Debian |
| | 2 | ---------------------- |
| | 3 | |
| | 4 | The following packages are built from the wxWidgets CVS source. |
| | 5 | |
| | 6 | libwxgtk wxGTK runtime shared libraries, including selected |
| | 7 | contrib libs. |
| | 8 | libwxgtk-dev extra files required for building wxGTK apps |
| | 9 | libwxgtk-dbg wxGTK libraries built with -g and __WXDEBUG__ |
| | 10 | |
| | 11 | libwxgtk-python Python binding to wxGTK (from 2.2.3 onward, this |
| | 12 | obsoletes the libwxgtk-python-contrib package as |
| | 13 | all python modules are built into a single monolith) |
| | 14 | |
| | 15 | wx-headers common header files for building wxWidgets apps |
| | 16 | wx-doc HTML version of the wxWidgets manual |
| | 17 | wx-examples wxWidgets and wxPython demos and samples (source) |
| | 18 | wx-i18n message catalogs for native language support |
| | 19 | |
| | 20 | |
| | 21 | Note that static libraries are no longer supplied in these |
| | 22 | packages. Please read, or have understood: |
| | 23 | http://people.redhat.com/drepper/no_static_linking.html |
| | 24 | among others before reporting this as a bug. |
| | 25 | |
| | 26 | The following binaries can be built from the source package |
| | 27 | with the mingw32 cross compiler, but are not currently |
| | 28 | distributed by Debian. If you feel that should change, |
| | 29 | please file a bug against the wxwidgets2.6 package, or |
| | 30 | append your views to a report already there if you're not |
| | 31 | the first to do so. |
| | 32 | |
| | 33 | [ you can check the current state of affairs at: |
| | 34 | http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wxwidgets2.6 ] |
| | 35 | |
| | 36 | Oh and, please do *not* file bug reports for these packages |
| | 37 | to the Debian bts. But do feel free to email me personally |
| | 38 | if you find problems and/or have patches to fix them. |
| | 39 | |
| | 40 | libwxmsw-dev mingw32-cross wxMSW libs. |
| | 41 | libwxmsw-dbg mingw32-cross wxMSW (debug) libs. |
| | 42 | wx-headers-msw extra headers needed for wxMSW. |
| | 43 | |
| | 44 | You can build these extra packages using the binary-cross target |
| | 45 | in debian/rules. |
| | 46 | |
| | 47 | |
| | 48 | It is also possible to build a libwxgtk-dbg-python package. |
| | 49 | There are some limitations (like this package cannot be installed |
| | 50 | concurrently with the release version), but some developers may |
| | 51 | find such a thing useful in any case. It will transparently |
| | 52 | replace the release package for installed apps that depend on the |
| | 53 | release package, but should NEVER be used when preparing packages |
| | 54 | for upload. This package may be created from the source using the |
| | 55 | binary-dbg-py target in debian/rules. (note that doing this will |
| | 56 | also destroy any release build that exists in the same tree, they |
| | 57 | cannot coexist there either yet) |
| | 58 | |
| | 59 | |
| | 60 | Finally, because all of these packages can take quite some time to |
| | 61 | build, the source package supports the use of distcc. The package |
| | 62 | builds will automatically parallelise to suit the number of hosts |
| | 63 | you have listed in DISTCC_HOSTS. This will work for both native |
| | 64 | and cross builds of the c++ libraries, if you have the relevant |
| | 65 | compilers on all your build hosts. wxPython builds cannot be |
| | 66 | parallelised at this stage and will run serially regardless of |
| | 67 | your configuration. |
| | 68 | |
| | 69 | |
| | 70 | -- Ron Lee <ron@debian.org>, Sun, 13 Feb 2000 18:40:00 +1030 |
| | 71 | |
projects / wxWidgets.git / blame_incremental