X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/e1293dcf96057ed7f7c5ada816377eaf19532c1e..1635893246a6454a51fcaea15dc3f1f960973c36:/debian/README.Debian diff --git a/debian/README.Debian b/debian/README.Debian index b33e502ffc..de079f50a8 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -3,7 +3,8 @@ wxwidgets for Debian The following packages are built from the wxWidgets CVS source. -libwxgtk wxGTK runtime shared libraries +libwxgtk wxGTK runtime shared libraries, including selected + contrib libs. libwxgtk-dev extra files and static libs for building wxGTK apps libwxgtk-dbg wxGTK libraries built with -g and __WXDEBUG__ @@ -11,9 +12,6 @@ libwxgtk-python Python binding to wxGTK (from 2.2.3 onward, this obsoletes the libwxgtk-python-contrib package as all python modules are built into a single monolith) -libwxgtk-contrib wxWin contrib runtime shared libs (built with wxGTK) -libwxgtk-contrib-dev extra files and static contrib libs for building apps - wx-headers common header files for building wxWidgets apps wx-doc HTML version of the wxWidgets manual wx-examples wxWidgets and wxPython demos and samples (source) @@ -38,6 +36,31 @@ libwxmsw-dev mingw32-cross wxMSW libs. libwxmsw-dbg mingw32-cross wxMSW (debug) libs. wx-headers-msw extra headers needed for wxMSW. + You can build these extra packages using the binary-cross target + in debian/rules. + + + It is also possible to build a libwxgtk-dbg-python package. + There are some limitations (like this package cannot be installed + concurrently with the release version), but some developers may + find such a thing useful in any case. It will transparently + replace the release package for installed apps that depend on the + release package, but should NEVER be used when preparing packages + for upload. This package may be created from the source using the + binary-dbg-py target in debian/rules. (note that doing this will + also destroy any release build that exists in the same tree, they + cannot coexist there either yet) + + + Finally, because all of these packages can take quite some time to + build, the source package supports the use of distcc. The package + builds will automatically parallelise to suit the number of hosts + you have listed in DISTCC_HOSTS. This will work for both native + and cross builds of the c++ libraries, if you have the relevant + compilers on all your build hosts. wxPython builds cannot be + parallelised at this stage and will run serially regardless of + your configuration. + -- Ron Lee , Sun, 13 Feb 2000 18:40:00 +1030