9103d280f9
to the default system location under /usr. This way the commands: wx-config --prefix=/usr/$(host) and wx-config --prefix=/usr --host=$(host) are much more congruent in their action. Another nail in the coffin for inplace hacks. Link $srcdir/include to the build dir so that --prefix=$build_dir really does point to a realistic looking installed development environment. I don't know why I didn't do this instead of (ab)using --exec-prefix to 'fix' this simple omission for so long. Probably because it is much more obvious if contrib is out of the picture. That makes it a little more work right now, but long term this is a very clean and correct thing to do. It completely absolves us of the two independent variables problem, and of the tree becoming bogus without actually being stale. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@29260 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 |
||
|---|---|---|
| .. | ||
| changelog | ||
| compat | ||
| control.in | ||
| copyright | ||
| libwxgtk-dbg-python.menu | ||
| libwxgtk-dbg-python.prerm | ||
| libwxgtk-dbg.postinst | ||
| libwxgtk-dbg.prerm | ||
| libwxgtk-dev.menu | ||
| libwxgtk-dev.postinst | ||
| libwxgtk-dev.prerm | ||
| libwxgtk-python.dirs | ||
| libwxgtk-python.docs | ||
| libwxgtk-python.menu | ||
| libwxgtk-python.postinst | ||
| libwxgtk-python.prerm | ||
| libwxmsw-dbg.postinst | ||
| libwxmsw-dbg.prerm | ||
| libwxmsw-dev.postinst | ||
| libwxmsw-dev.prerm | ||
| lintian-override.in | ||
| README.Debian | ||
| README.examples | ||
| rules | ||
| wx-config.1 | ||
| wx-doc.doc-base | ||
| wx-doc.docs | ||
| wx-examples.examples | ||
| wxPython-tools.1 | ||
| wxrc-tools.1 | ||
These examples are provided as extended documentation for the wxWidgets package. If you wish to actually run them rather than just browse them as documents you should copy them into a working directory elsewhere first. Note that some of them will attempt to write to the current working directory, or to the home directory of the user they are run as. Some of the files have been compressed in accordance with Debian policy regarding documentation, you will need to uncompress such files before building or executing them. The examples provided here typically show a minimal implementation of the feature(s) they are demonstrating. There are examples of more complete (mini) applications, available in the /wxPython/samples and /demos directories of the wxWidgets cvs repository (which is browsable via http://cvs.wxwidgets.org), or of course you can always apt-get the source of any wx using package for some less contrived examples of real world wx applications. Ron