X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/094e328c21fce0213b884092e9812ebf250ae1f1..61c213fe224da24ce33c9187263e75a17ca83a04:/debian/README.Debian?ds=sidebyside diff --git a/debian/README.Debian b/debian/README.Debian index 1075a65747..f36922339b 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -1,38 +1,37 @@ -wxwindows for Debian +wxwidgets for Debian ---------------------- -The following packages are built from the wxWindows CVS source. +The following packages are built from the wxWidgets CVS source. -libwxbase wxBase runtime shared libraries -libwxbase-dev extra files and static libs for building wxBase apps -libwxbase-dbg wxBase libraries built with -g and __WXDEBUG__ - -libwxgtk wxGTK runtime shared libraries -libwxgtk-dev extra files and static libs for building wxGTK apps +libwxgtk wxGTK runtime shared libraries, including selected + contrib libs. +libwxgtk-dev extra files required for building wxGTK apps libwxgtk-dbg wxGTK libraries built with -g and __WXDEBUG__ 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) -wxwin-contrib wxWin contrib runtime shared libs (built with wxGTK) -wxwin-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) +wx-i18n message catalogs for native language support -wxwin-headers common header files for building wxWindows apps -wxwin-doc HTML version of the wxWindows manual -wxwin-examples wxWindows and wxPython demos and samples (source) -wxwin-i18n message catalogs for native language support + Note that static libraries are no longer supplied in these + packages. Please read, or have understood: + http://people.redhat.com/drepper/no_static_linking.html + among others before reporting this as a bug. - The following three can be built from the source package + The following binaries can be built from the source package with the mingw32 cross compiler, but are not currently distributed by Debian. If you feel that should change, - please file a bug against the wxwindows2.4 package, or + please file a bug against the wxwidgets2.6 package, or append your views to a report already there if you're not the first to do so. [ you can check the current state of affairs at: - http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wxwindows2.4 ] + http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wxwidgets2.6 ] Oh and, please do *not* file bug reports for these packages to the Debian bts. But do feel free to email me personally @@ -40,13 +39,32 @@ wxwin-i18n message catalogs for native language support libwxmsw-dev mingw32-cross wxMSW libs. libwxmsw-dbg mingw32-cross wxMSW (debug) libs. -libwxbase-msw-dev mingw32-cross wxBase libs. -libwxbase-msw-dbg mingw32-cross wxBase (debug) libs. -wxwin-headers-msw extra headers needed for wxMSW. +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) + -libwxgtk-univ wxUniversal for Gtk. NOTE this package is obsolete - and will be replaced by wxX11 and wxX11-univ at - some future time. + 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