4
The following packages are built from the wxWidgets CVS source.
6
libwxbase wxBase runtime shared libraries
7
libwxbase-dev extra files and static libs for building wxBase apps
8
libwxbase-dbg wxBase libraries built with -g and __WXDEBUG__
10
libwxgtk wxGTK runtime shared libraries, including selected
12
libwxgtk-dev extra files required for building wxGTK apps
13
libwxgtk-dbg wxGTK libraries built with -g and __WXDEBUG__
15
python-wxgtk Python binding to wxGTK (from 2.2.3 onward, this
16
obsoletes the libwxgtk-python-contrib package as
17
all python modules are built into a single monolith)
18
python-wxversion The wxversion.py version selector, new to wxPython2.6
19
python-wxtools The ancillary tools from the wxPython distribution.
21
wx-common common helper files and support applications.
22
wx-headers common header files for building wxWidgets apps
23
wx-doc HTML version of the wxWidgets manual
24
wx-examples wxWidgets and wxPython demos and samples (source)
25
wx-i18n message catalogs for native language support
28
Note that static libraries are no longer supplied in these
29
packages. Please read, or have understood:
30
http://people.redhat.com/drepper/no_static_linking.html
31
among others before reporting this as a bug.
33
The following binaries can be built from the source package
34
with the mingw32 cross compiler, but are not distributed
35
as a part of the main Debian distribution.
37
Please do *not* file bug reports for these packages to the
38
Debian bts. But do feel free to email me personally if you
39
find problems and/or have patches to fix them.
41
libwxmsw-dev mingw32-cross wxMSW libs.
42
libwxmsw-dbg mingw32-cross wxMSW (debug) libs.
43
wx-headers-msw extra headers needed for wxMSW.
45
You can build these extra packages using the binary-cross target
49
It is also possible to build a python-wxgtk-dbg package.
50
There are some limitations (like this package cannot be installed
51
concurrently with the release version), but some developers may
52
find such a thing useful in any case. It will transparently
53
replace the release package for installed apps that depend on the
54
release package, but should NEVER be used when preparing packages
55
for upload. This package may be created from the source using the
56
binary-dbg-py target in debian/rules. (note that doing this will
57
also destroy any release build that exists in the same tree, they
58
cannot coexist there either yet)
61
Finally, because all of these packages can take quite some time to
62
build, the source package supports the use of distcc. The package
63
builds will automatically parallelise to suit the number of hosts
64
you have listed in DISTCC_HOSTS. This will work for both native
65
and cross builds of the c++ libraries, if you have the relevant
66
compilers on all your build hosts.
67
You may override that heuristic by setting the CONCURRENCY_LEVEL
68
environment variable to the number of jobs you wish make to fork.
69
That variable is also supported by the kernel-package scripts and
70
is respected for consistency here.
72
wxPython builds cannot be parallelised at this stage and will run
73
serially regardless of your configuration.
76
-- Ron Lee <ron@debian.org>, Sun, 13 Feb 2000 18:40:00 +1030