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