+ You can build these extra packages using the binary-cross target
+ in debian/rules.
+
+
+ It is also possible to build a python-wxgtk-dbg 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.
+ You may override that heuristic by setting the CONCURRENCY_LEVEL
+ environment variable to the number of jobs you wish make to fork.
+ That variable is also supported by the kernel-package scripts and
+ is respected for consistency here.
+
+ wxPython builds cannot be parallelised at this stage and will run
+ serially regardless of your configuration.
+