Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions 8 Packages Projects Releases Wiki Activity

Updated links and mailing list addresses.

Browse Source
This commit is contained in:
Bryan Petty
2015-10-30 20:06:09 -06:00
parent d61b52a60e
commit 0b2263c25d
38 changed files with 261 additions and 294 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -4,7 +4,7 @@ About
wxWidgets is a free and open source cross-platform C++ framework
for writing advanced GUI applications using native controls.
![wxWidgets Logo](http://www.wxwidgets.org/assets/img/header-logo.png)
![wxWidgets Logo](https://www.wxwidgets.org/assets/img/header-logo.png)
wxWidgets allows you to write native-looking GUI applications for
@@ -13,7 +13,7 @@ the differences in the non-GUI aspects between them. It is free
for the use in both open source and commercial applications, comes
with the full, easy to read and modify, source and extensive
documentation and a collection of more than a hundred examples.
You can learn more about wxWidgets at http://www.wxwidgets.org/
You can learn more about wxWidgets at https://www.wxwidgets.org/
and read its documentation online at http://docs.wxwidgets.org/
@@ -48,10 +48,11 @@ Further information
If you are looking for support, you can get it from
- wx-users [mailing list](http://www.wxwidgets.org/support/mailing-lists/)
- wxForum at http://forums.wxwidgets.org/
- #wxwidgets IRC channel
- http://stackoverflow.com/ if you tag your question with "wxwidgets"
- [Mailing Lists](https://www.wxwidgets.org/support/mailing-lists/)
- [Discussion Forums][https://forums.wxwidgets.org/]
- [#wxwidgets IRC channel][https://www.wxwidgets.org/support/irc/]
- Stack Overflow (tag your questions with @c wxwidgets):
https://stackoverflow.com/questions/tagged/wxwidgets
- Please report bugs at http://trac.wxwidgets.org/newticket
We would also gladly welcome [your contributions](CONTRIBUTING.md).

4
build/aclocal/bakefile.m4
View File

@@ -27,7 +27,7 @@ dnl
dnl ---------------------------------------------------------------------------
dnl Lots of compiler & linker detection code contained here was taken from
dnl wxWidgets configure.in script (see http://www.wxwidgets.org)
dnl wxWidgets configure.in script (see https://www.wxwidgets.org)
dnl ---------------------------------------------------------------------------
@@ -946,7 +946,7 @@ while test ${D}# -gt 0; do
args="${D}{args} ${D}1 ${D}2"
shift
;;
-arch|-isysroot)
# collect these options and values
ldargs="${D}{ldargs} ${D}1 ${D}2"

3
build/bakefiles/wxpresets/bakefile_quickstart.txt
View File

@@ -261,6 +261,7 @@ This concludes our basic tutorial of the cross-platform Bakefile build system
management tool. From here, please be sure to take a good look at the Bakefile
documentation to see what else it is capable of. Please post questions to the
bakefile-devel@lists.sourceforge.net list, or if you have questions specific
to the wx template Bakefile, send an email to wx-users@lists.wxwidgets.org.
to the wx template Bakefile, send an email to the wxWidgets users mailing list:
https://www.wxwidgets.org/support/mailing-lists/
Enjoy using Bakefile!

2
build/buildbot/config/example.xml
View File

@@ -12,7 +12,7 @@
column in the waterfall display.
For full documentation see:
http://www.wxwidgets.org/wiki/index.php/Development:_Buildbot
https://wiki.wxwidgets.org/Development:_Buildbot
-->
<bot xmlns:xi="http://www.w3.org/2001/XInclude">

2
build/buildbot/config/push.xml
View File

@@ -10,7 +10,7 @@
This allows the logs from builds done elsewhere to be included in the
buildbot results, see:
http://www.wxwidgets.org/wiki/index.php/Development:_Buildbot#Sending_in_Logs_from_Builds_Done_Elsewhere
https://wiki.wxwidgets.org/Development:_Buildbot#Sending_in_Logs_from_Builds_Done_Elsewhere
-->
<bot xmlns:xi="http://www.w3.org/2001/XInclude">

8
build/tools/wxwidgets.iss
View File

@@ -25,9 +25,9 @@
AppName=wxWidgets
AppVerName=wxWidgets {#WX_VERSION}
AppPublisher=wxWidgets
AppPublisherURL=http://www.wxwidgets.org
AppSupportURL=http://www.wxwidgets.org
AppUpdatesURL=http://www.wxwidgets.org
AppPublisherURL=https://www.wxwidgets.org
AppSupportURL=https://www.wxwidgets.org
AppUpdatesURL=https://www.wxwidgets.org
DefaultDirName={sd}\wxWidgets-{#WX_VERSION}
DefaultGroupName=wxWidgets {#WX_VERSION}
UsePreviousAppDir=no
@@ -47,7 +47,7 @@ SolidCompression=yes
Source: "{#WXW_DIR}\*"; DestDir: "{app}"; Excludes: "cocoa,dfb,gtk,gtk1,motif,osx,wxWindows.xcod*,x11,distrib"; Flags: ignoreversion recursesubdirs createallsubdirs
[INI]
Filename: "{app}\wx.url"; Section: "InternetShortcut"; Key: "URL"; String: "http://www.wxwidgets.org"
Filename: "{app}\wx.url"; Section: "InternetShortcut"; Key: "URL"; String: "https://www.wxwidgets.org"
[Icons]
Name: "{group}\{cm:ProgramOnTheWeb,wxWidgets}"; Filename: "{app}\wx.url"

17
configure vendored
View File

@@ -2,7 +2,7 @@
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.69 for wxWidgets 3.1.0.
#
# Report bugs to <wx-dev@lists.wxwidgets.org>.
# Report bugs to <wx-dev@googlegroups.com>.
#
#
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@@ -267,7 +267,7 @@ fi
$as_echo "$0: be upgraded to zsh 4.3.4 or later."
else
$as_echo "$0: Please tell bug-autoconf@gnu.org and
$0: wx-dev@lists.wxwidgets.org about your system, including
$0: wx-dev@googlegroups.com about your system, including
$0: any error possibly output before this message. Then
$0: install a modern shell, or manually run the script
$0: under such a shell if you do have one."
@@ -582,7 +582,7 @@ PACKAGE_NAME='wxWidgets'
PACKAGE_TARNAME='wxwidgets'
PACKAGE_VERSION='3.1.0'
PACKAGE_STRING='wxWidgets 3.1.0'
PACKAGE_BUGREPORT='wx-dev@lists.wxwidgets.org'
PACKAGE_BUGREPORT='wx-dev@googlegroups.com'
PACKAGE_URL=''
ac_unique_file="wx-config.in"
@@ -2401,7 +2401,7 @@ Some influential environment variables:
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Report bugs to <wx-dev@lists.wxwidgets.org>.
Report bugs to <wx-dev@googlegroups.com>.
_ACEOF
ac_status=$?
fi
@@ -3132,7 +3132,7 @@ $as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
( $as_echo "## ----------------------------------------- ##
## Report this to wx-dev@lists.wxwidgets.org ##
## Report this to wx-dev@googlegroups.com ##
## ----------------------------------------- ##"
) | sed "s/^/$as_me: WARNING: /" >&2
;;
@@ -4034,8 +4034,8 @@ case "${host}" in
*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: *** System type ${host} is unknown, assuming generic Unix and continuing nevertheless." >&5
$as_echo "$as_me: WARNING: *** System type ${host} is unknown, assuming generic Unix and continuing nevertheless." >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: *** Please report the build results to wx-dev@lists.wxwidgets.org." >&5
$as_echo "$as_me: WARNING: *** Please report the build results to wx-dev@lists.wxwidgets.org." >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: *** Please report the build results to wx-dev@googlegroups.com." >&5
$as_echo "$as_me: WARNING: *** Please report the build results to wx-dev@googlegroups.com." >&2;}
DEFAULT_DEFAULT_wxUSE_X11=1
DEFAULT_wxUSE_SHARED=no
@@ -40966,7 +40966,7 @@ $config_headers
Configuration commands:
$config_commands
Report bugs to <wx-dev@lists.wxwidgets.org>."
Report bugs to <wx-dev@googlegroups.com>."
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
@@ -41903,4 +41903,3 @@ echo " libmspack ${wxUSE_LIBMSPAC
echo " sdl ${wxUSE_LIBSDL}"
echo ""

10
configure.in
View File

@@ -14,7 +14,7 @@ dnl ---------------------------------------------------------------------------
dnl initialization
dnl ---------------------------------------------------------------------------
AC_INIT([wxWidgets], [3.1.0], [wx-dev@lists.wxwidgets.org])
AC_INIT([wxWidgets], [3.1.0], [wx-dev@googlegroups.com])
dnl the file passed to AC_CONFIG_SRCDIR should be specific to our package
AC_CONFIG_SRCDIR([wx-config.in])
@@ -299,7 +299,7 @@ case "${host}" in
*)
AC_MSG_WARN([*** System type ${host} is unknown, assuming generic Unix and continuing nevertheless.])
AC_MSG_WARN([*** Please report the build results to wx-dev@lists.wxwidgets.org.])
AC_MSG_WARN([*** Please report the build results to wx-dev@googlegroups.com.])
DEFAULT_DEFAULT_wxUSE_X11=1
DEFAULT_wxUSE_SHARED=no
@@ -1205,7 +1205,7 @@ elif test "x$wxUSE_MACOSX_VERSION_MIN" = "x"; then
wxUSE_MACOSX_VERSION_MIN=10.5
fi
if test "x$MACOSX_SDK_OPTS" != "x"; then
if test "x$MACOSX_SDK_OPTS" != "x"; then
eval "CC=\"$CC $MACOSX_SDK_OPTS\""
eval "CXX=\"$CXX $MACOSX_SDK_OPTS\""
eval "LD=\"$LD $MACOSX_SDK_OPTS\""
@@ -7286,12 +7286,12 @@ if test "$wxUSE_MEDIACTRL" = "yes" -o "$wxUSE_MEDIACTRL" = "auto"; then
USE_MEDIA=0
fi
elif test "$wxUSE_MAC" = 1; then
elif test "$wxUSE_MAC" = 1; then
if test "$wxUSE_OSX_IPHONE" = 1; then
dnl this will also be used for cocoa in the future
GST_LIBS="-framework AVFoundation -framework CoreMedia"
else
dnl We always have the necessary libraries under Mac
dnl We always have the necessary libraries under Mac
dnl but we need to link with it explicitly.
GST_LIBS="-framework QTKit"
fi

2
distrib/autopackage/wxgtk.apspec.in
View File

@@ -26,7 +26,7 @@ ShortName: wxgtk
Maintainer: Francesco Montorsi <frm@users.sourceforge.net>
Packager: Francesco Montorsi <frm@users.sourceforge.net>
Summary: Library for cross-platform GUI programming (gtk2-unicode-release port)
URL: http://www.wxwidgets.org/
URL: https://www.wxwidgets.org/
Licence: wxWindows licence
SoftwareVersion: @PACKAGE_VERSION@
PackageVersion: 1

7
docs/base/readme.txt
View File

@@ -114,11 +114,8 @@ documentation instead.
Support for wxBase is available from the same places as for wxWidgets itself,
namely:
* Usenet newsgroup comp.soft-sys.wxwindows
* Mailing lists: see http://lists.wxwidgets.org/ for more information
* WWW page: http://www.wxwidgets.org/
* Website: https://www.wxwidgets.org/
* Mailing Lists: https://www.wxwidgets.org/support/mailing-lists/
Hope you will find wxBase useful!

8
docs/contributing/how-to-release.md
View File

@@ -98,17 +98,17 @@ Create http://docs.wxwidgets.org/x.y.z/ (ask Bryan to do it if not done yet).
## Announcement
Update http://www.wxwidgets.org, usually a news item is enough but something
Update https://www.wxwidgets.org, usually a news item is enough but something
more can be called for for major releases.
Post `docs/publicity/announce.txt` at least to wx-announce@googlegroups.com and
to wx-users for the important releases.
Submit a link to http://www.reddit.com/r/programming
Submit a link to https://www.reddit.com/r/programming
Submit to http://isocpp.org/blog/suggest
Submit to https://isocpp.org/blog/suggest
For major releases, submit the announcement to http://slashdot.org/submission
For major releases, submit the announcement to https://slashdot.org/submission
Modify the links at downloads/index.html to point to the new release. Also
update the release date on this page.

4
docs/dfb/install.txt
View File

@@ -83,6 +83,6 @@ Bug reports
-----------
Please send bug reports with a description of your environment,
compiler and the error message(s) to the wxwin-developers mailing list at:
compiler and the error message(s) to the developers mailing list at:
wx-dev@lists.wxwidgets.org
https://www.wxwidgets.org/support/mailing-lists/

2
docs/doxygen/custom_header.html
View File

@@ -25,7 +25,7 @@ $extrastylesheet
<tr>
<!--BEGIN PROJECT_LOGO-->
<td id="projectlogo">
<a href="http://www.wxwidgets.org/" target="_new">
<a href="https://www.wxwidgets.org/" target="_new">
<img alt="wxWidgets" src="$relpath$$projectlogo"/>
</a>
</td>

22
docs/doxygen/mainpages/introduction.h
View File

@@ -26,7 +26,7 @@ in 2013. Currently wxWidgets is developed and maintained by Julian Smart, Vadim
Zeitlin, Stefan Csomor, Robert Roebling, Vaclav Slavik and many others.
More information about wxWidgets is available on its web site at
http://www.wxwidgets.org.
https://www.wxwidgets.org.
@@ -111,21 +111,21 @@ configurations but at least 1GB and possibly more is required.
@section page_introduction_where Where to get wxWidgets and support for it
The download links can be found at http://www.wxwidgets.org. The primary
download location is https://sourceforge.net/downloads/wxwindows/ and there is
also an FTP mirror at ftp://ftp.wxwidgets.org/pub/. Additionally, the latest
version can always be retrieved from our version control system using Git
(https://github.com/wxWidgets/wxWidgets).
The download links can be found at https://www.wxwidgets.org. The primary
download location is https://github.com/wxWidgets/wxWidgets/releases/latest.
Additionally, the latest version can always be retrieved from our version
control system using Git (https://github.com/wxWidgets/wxWidgets).
wxWidgets documentation that you are reading is also available online at
http://docs.wxwidgets.org/trunk/ and please also visit our wiki at
http://wiki.wxwidgets.org/ for user-contributed contents.
https://wiki.wxwidgets.org/ for user-contributed contents.
And if you have any questions, you can join wxWidgets community using
- Web-based <a href="http://forums.wxwidgets.org/">wxForum</a>.
- <a href="http://www.wxwidgets.org/support/maillst2.htm">Mailing lists</a>.
- @c #wxwidgets IRC channel.
- Or asking questions with @c wxwidgets tag on http://stackoverflow.com/
- Web-based <a href="https://forums.wxwidgets.org/">wxForum</a>
- <a href="https://www.wxwidgets.org/support/mailing-lists/">Mailing lists</a>
- <a href="https://www.wxwidgets.org/support/irc/">#wxwidgets IRC Channel</a>
- Or asking questions with @c wxwidgets tag on Stack Overflow:
https://stackoverflow.com/questions/tagged/wxwidgets
*/

4
docs/doxygen/mainpages/translations.h
View File

@@ -467,8 +467,8 @@ Here are the steps you should follow:
and it will be added to the next wxWidgets release or snapshot.
In addition, please consider subscribing to the very low volume
<a href="http://lists.wxwidgets.org/mailman/listinfo/wx-translators">
wxWidgets translators</a> mailing list on which the news especially important
<a href="https://www.wxwidgets.org/support/mailing-lists/">
wxWidgets translators mailing list</a> on which the news especially important
for the translators are announced.
Thank you in advance for your help!

12
docs/doxygen/mainpages/utilities.h
View File

@@ -16,11 +16,12 @@ are available to the users in the @c utils hierarchy (even if some of them are
explicitly conceived for wxWidgets maintainance and will probably be of
little use to others).
Please note that these utilities do represent only the utilities developed
and maintained by the wxWidgets team.
There are lots of other user-contributed and user-maintained packages;
see the wxWidgets download page: http://www.wxwidgets.org/downloads
or directly http://wxcode.sourceforge.net or http://www.wxcommunity.com/ .
Please note that these utilities only represent the utilities developed and
maintained by the wxWidgets team. There are lots of other user-contributed and
user-maintained packages such as:
@li http://wxcode.sourceforge.net
@li https://forums.wxwidgets.org/viewforum.php?f=20
@@ -87,4 +88,3 @@ See @ref overview_xrc for more info.
You can find it under @c utils/wxrc.
*/

3
docs/doxygen/overviews/filesystem.h
View File

@@ -42,7 +42,8 @@ Locations (aka filenames aka addresses) are constructed from four parts:
@li @b protocol - handler can recognize if it is able to open a
file by checking its protocol. Examples are "http", "file" or "ftp".
@li <b>right location</b> - is the name of file within the protocol.
In "http://www.wxwidgets.org/index.html" the right location is "//www.wxwidgets.org/index.html".
In "https://www.wxwidgets.org/index.html" the right location is
"//www.wxwidgets.org/index.html".
@li @b anchor - an anchor is optional and is usually not present.
In "index.htm#chapter2" the anchor is "chapter2".
@li <b>left location</b> - this is usually an empty string.

2
docs/doxygen/overviews/python.h
View File

@@ -453,6 +453,6 @@ probably the best source is the wxPython-users mail list. You can view the
archive or subscribe by going to http://wxpython.org/maillist.php
Or you can send mail directly to the list using this address:
wxpython-users@lists.wxwidgets.org
wxpython-users@googlegroups.com
*/

26
docs/gtk/readme.txt
View File

@@ -19,16 +19,16 @@ is done on that port anymore and support for GTK+ 1.2 will
probably be dropped entirely. Indeed, one of the major steps
in the development cycle leading up to wxWidgets 2.8 was
that the codebase for GTK+ 1.2 and GTK+ 2.0 were separated
so that improvements and clean-ups to the GTK+ 2.0 port
so that improvements and clean-ups to the GTK+ 2.0 port
could be done without caring for GTK+ 1.2.
More info about the wxWidgets project (including all the
other ports and version of wxWidgets) can be found at the
main wxWidgets homepage at:
http://www.wxwidgets.org/
Information on how to install can be found in the file
https://www.wxwidgets.org/
Information on how to install can be found in the file
INSTALL.txt, but if you cannot wait, this should work on
many systems:
@@ -51,23 +51,21 @@ different builds of it (for example with and without debug) in
parallel. If you build in the source directory, don't forget to
do "make clean" before changing the configuration!
When you run into problems, please read the INSTALL.txt and
When you run into problems, please read the INSTALL.txt and
follow those instructions. If you still don't have any success,
please send a bug report to one of our mailing list, INCLUDING
A DESCRIPTION OF YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR
VERSION OF GTK, WXGTK, WHAT DISTRIBUTION YOU USE AND WHAT ERROR
please send a bug report to one of our mailing list, INCLUDING
A DESCRIPTION OF YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR
VERSION OF GTK, WXGTK, WHAT DISTRIBUTION YOU USE AND WHAT ERROR
WAS REPORTED. I know this has no effect, but I tried...
Please send problems concerning installation, feature requests,
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. These can
be found at http://www.wxwidgets.org and more specifically at
http://lists.wxwidgets.org.
be found at https://www.wxwidgets.org/support/mailing-lists/
wxWidgets doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
wxWidgets doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
claim to be suitable for any special or general purpose.
Regards,
Robert Roebling

10
docs/index.htm
View File

@@ -93,7 +93,7 @@
<p>The wxWidgets manual is available in various formats; the availability of
the following formats depends on what you've downloaded from the
<a href="http://www.wxwidgets.org">wxWidgets website</a>:</p>
<a href="https://www.wxwidgets.org">wxWidgets website</a>:</p>
<ul>
<li><a href="doxygen/out/html/index.html">HTML</a></li>
@@ -113,13 +113,13 @@
programming:</p>
<ul>
<li><a href="http://www.wxwidgets.org">The wxWidgets website</a>: Contains
<li><a href="https://www.wxwidgets.org">The wxWidgets website</a>: Contains
FAQs, tutorials, info about the mailing lists, and in general
everything related to the wxWidgets world is linked here.</li>
<li><a href="http://forums.wxwidgets.org/">The wxWidgets forum</a>:
<li><a href="https://forums.wxwidgets.org/">The wxWidgets forum</a>:
Provides a discussion board about various wxWidgets topics (contains
also <em>localized</em> forums).</li>
<li><a href="http://wiki.wxwidgets.org/">The wxWiki</a>: A user-editable
<li><a href="https://wiki.wxwidgets.org/">The wxWiki</a>: A user-editable
website with lots of tutorials, links to external tools, resources,
etc.</li>
</ul>
@@ -138,7 +138,7 @@
<p>Todo List for wxWidgets:</p>
<ul>
<li><a href="http://wiki.wxwidgets.org/Development:_Todo_List">wxWiki Todo List</a></li>
<li><a href="https://wiki.wxwidgets.org/Development:_Todo_List">wxWiki Todo List</a></li>
<li><a href="doxygen/out/html/todo.html">Documentation Todo List</a></li>
</ul>

105
docs/motif/install.txt
View File

@@ -8,9 +8,9 @@ IMPORTANT NOTE:
osname.txt for your platform if it exists) carefully before
mailing wx-users or the author. Preferably, try to fix the
problem first and then send a patch to the author.
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
example: wxMotif 2.8.1, gcc 2.95.4, Redhat 6.1
First steps
@@ -37,7 +37,7 @@ First steps
Using configure is the only way to build the library. If it doesn't
work for you for whatever reason, please report it (together with detailed
information about your platform and the (relevant part of) contents of
config.log file) to wx-dev@lists.wxwidgets.org.
config.log file).
COMPILING USING CONFIGURE
@@ -46,7 +46,7 @@ COMPILING USING CONFIGURE
* The simplest case
-------------------
If you compile wxWidgets on Linux for the first time and don't like to read
If you compile wxWidgets on Linux for the first time and don't like to read
install instructions just do (in the base dir):
> ./configure --with-motif
@@ -74,11 +74,11 @@ If you want to remove wxWidgets on Unix you can do this:
* The expert case
-----------------
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and Motif, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and Motif, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
of wxWidgets - you may also want to create different versions of wxWidgets
and test them concurrently. Most typically, this would be a version configured
and test them concurrently. Most typically, this would be a version configured
with --enable-debug and one without.
For building three versions (one GTK, one Motif and a debug version of the GTK
@@ -132,11 +132,11 @@ g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo
The Unix variants of wxWidgets use GNU configure. If you have problems with
your make use GNU make instead.
If you have general problems with installation, see the wxWidgets website at
If you have general problems with installation, see the wxWidgets website at
http://www.wxwidgets.org/
for newest information. If you still don't have any success, please send a bug
https://www.wxwidgets.org/
for newest information. If you still don't have any success, please send a bug
report to one of our mailing lists (see my homepage) INCLUDING A DESCRIPTION OF
YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR VERSION OF MOTIF, WXMOTIF, WHAT
DISTRIBUTION YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect,
@@ -151,8 +151,8 @@ most of the Motif API without the licence restrictions of Motif.
You can get the newest version of the Lesstif from the lesstif homepage at:
http://www.lesstif.org/
http://lesstif.sourceforge.net/
* Additional libraries
----------------------
@@ -162,7 +162,7 @@ Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
many aspects. As of writing this, virtually all Linux distributions have
correct glibc 2 support.
You can disable thread support by running
You can disable thread support by running
./configure --disable-threads
make
@@ -170,7 +170,7 @@ su <type root password>
make install
ldconfig
exit
* Building wxMotif on OS/2
--------------------------
@@ -197,7 +197,7 @@ Set MAKESHELL or MAKE_SHELL (which one is needed depends on the version of
make) to a Unix like shell, e.g.
SET MAKESHELL=ash
If you have a really deficient version of GNU make, it might even be
necessary to set SHELL or even COMSPEC to a unix like shell as well.
necessary to set SHELL or even COMSPEC to a unix like shell as well.
Depending on your installation you might want to also set INSTALL, for me
it tends to try to use the system's tcpip\pcomos\install.exe which causes
problems, e.g.
@@ -217,16 +217,16 @@ explicitly set CFLAGS prior to running configure.
-------------------------
Using the SGI native compilers, it is recommended that you
also set CFLAGS and CXXFLAGS before running configure. These
also set CFLAGS and CXXFLAGS before running configure. These
should be set to :
CFLAGS="-mips3 -n32"
CFLAGS="-mips3 -n32"
CXXFLAGS="-mips3 -n32"
This is essential if you want to use the resultant binaries
on any other machine than the one it was compiled on. If you
have a 64bit machine (Octane) you should also do this to ensure
you don't accidently build the libraries as 64bit (which is
This is essential if you want to use the resultant binaries
on any other machine than the one it was compiled on. If you
have a 64bit machine (Octane) you should also do this to ensure
you don't accidently build the libraries as 64bit (which is
untested).
The SGI native compiler support has only been tested on Irix 6.5.
@@ -263,16 +263,16 @@ to see all the options please use:
./configure --help
The basic philosophy is that if you want to use different
configurations, like a debug and a release version,
configurations, like a debug and a release version,
or use the same source tree on different systems,
you have only to change the environment variable OSTYPE.
(Sadly this variable is not set by default on some systems
in some shells - on SGI's for example). So you will have to
set it there. This variable HAS to be set before starting
configure, so that it knows which system it tries to
in some shells - on SGI's for example). So you will have to
set it there. This variable HAS to be set before starting
configure, so that it knows which system it tries to
configure for.
Configure will complain if the system variable OSTYPE has
Configure will complain if the system variable OSTYPE has
not been defined. And Make in some circumstances as well...
@@ -290,7 +290,7 @@ You have to add --with-motif on platforms, where Motif is
not the default (on Linux, configure will default to GTK).
--with-motif Use either Motif or Lesstif
Configure will look for both.
Configure will look for both.
The following options handle the kind of library you want to build.
@@ -310,29 +310,29 @@ The following options handle the kind of library you want to build.
such as Sun with gcc 2.8.X which
would otherwise produce segvs.
--enable-profile Add profiling info to the object
--enable-profile Add profiling info to the object
files. Currently broken, I think.
--enable-no_rtti Enable compilation without creation of
C++ RTTI information in object files.
This will speed-up compilation and reduce
C++ RTTI information in object files.
This will speed-up compilation and reduce
binary size.
--enable-no_exceptions Enable compilation without creation of
C++ exception information in object files.
This will speed-up compilation and reduce
C++ exception information in object files.
This will speed-up compilation and reduce
binary size. Also fewer crashes during the
actual compilation...
--enable-no_deps Enable compilation without creation of
dependency information.
--enable-permissive Enable compilation without checking for strict
ANSI conformance. Useful to prevent the build
dying with errors as soon as you compile with
Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
--enable-mem_tracing Add built-in memory tracing.
--enable-dmalloc Use the dmalloc memory debugger.
Read more at www.letters.com/dmalloc/
@@ -349,7 +349,7 @@ The following options handle the kind of library you want to build.
useful internal debugging tricks (such
as automatically reporting illegal calls)
to work. Note that program and library
must be compiled with the same debug
must be compiled with the same debug
options.
* Feature Options
@@ -360,7 +360,7 @@ in wxWidgets snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
you'll be surprised at its immense size. This can sometimes be
drastically reduced by removing features from wxWidgets that
drastically reduced by removing features from wxWidgets that
are not used in your program. The most relevant such features
are
@@ -394,7 +394,7 @@ are
--disable-validators Disables validators.
--disable-accel Disables accel.
Apart from disabling certain features you can very often "strip"
the program of its debugging information resulting in a significant
reduction in size.
@@ -409,13 +409,13 @@ of all configurable options.
The following must be done in the base directory (e.g. ~/wxMotif
or ~/wxWin or whatever)
Now the makefiles are created (by configure) and you can compile
Now the makefiles are created (by configure) and you can compile
the library by typing:
make
make yourself some coffee, as it will take some time. On an old
Pentium 200 around 40 minutes. During compilation, you may get a few
Pentium 200 around 40 minutes. During compilation, you may get a few
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
@@ -426,12 +426,12 @@ Then you may install the library and its header files under
have to log in as root (i.e. run "su" and enter the root
password) and type
make install
make install
You can remove any traces of wxWidgets by typing
make uninstall
If you want to save disk space by removing unnecessary
object-files:
@@ -453,12 +453,12 @@ like this
CXX = g++
minimal: minimal.o
$(CXX) -o minimal minimal.o `wx-config --libs`
$(CXX) -o minimal minimal.o `wx-config --libs`
minimal.o: minimal.cpp
$(CXX) `wx-config --cxxflags` -c minimal.cpp -o minimal.o
clean:
clean:
rm -f *.o minimal
If your application uses only some of wxWidgets libraries, you can
@@ -467,7 +467,7 @@ specify required libraries when running wx-config. For example,
with libraries required by core GUI classes and wxHTML classes. See
the manual for more information on the libraries.
2) The other way creates a project within the source code
2) The other way creates a project within the source code
directories of wxWidgets. For this endeavour, you'll need
GNU autoconf version 2.14 and add an entry to your Makefile.in
to the bottom of the configure.in script and run autoconf
@@ -535,9 +535,8 @@ Bug reports
-----------
Please send bug reports with a description of your environment,
compiler and the error message(s) to the wxwin-developers mailing list at:
compiler and the error message(s) to the developers mailing list at:
wx-dev@lists.wxwidgets.org
https://www.wxwidgets.org/support/mailing-lists/
Julian Smart, Robert Roebling and Vadim Zeitlin, November 1999.

17
docs/motif/readme.txt
View File

@@ -6,9 +6,9 @@ You have downloaded the Motif port of the wxWidgets GUI library.
More information about the wxWidgets project as a whole
can be found at:
http://www.wxwidgets.org/
Information on how to install can be found in the file
https://www.wxwidgets.org/
Information on how to install can be found in the file
install.txt, but if you cannot wait, this should work on
many systems:
@@ -31,20 +31,19 @@ DISTRIBUTION YOU USE AND WHAT ERROR WAS REPORTED.
Alternatively, you may also use the bug reporting system
linked from the wxWidgets web page.
The library produced by the install process will be called
The library produced by the install process will be called
libwx_motif.a (static) and libwx_motif-2.6.so.0.0.0 (shared) so that
once a binary incompatible version of wxWidgets/Motif comes out
once a binary incompatible version of wxWidgets/Motif comes out
we'll augment the library version number to avoid linking problems.
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from www.wxwidgets.org.
wxWidgets/Motif doesn't come with any guarantee whatsoever. It might
wxWidgets/Motif doesn't come with any guarantee whatsoever. It might
crash your hard disk or destroy your monitor. It doesn't claim to be
suitable for any special or general purpose.
Regards,
The wxWidgets team

5
docs/msw/install.txt
View File

@@ -386,8 +386,7 @@ UNICODE=0
(ditto).
WXUNIV=1
Build wxUniversal instead of native wxMSW (see
http://www.wxwidgets.org/wxuniv.htm for more information).
Build wxUniversal instead of native wxMSW
MONOLITHIC=1
Starting with version 2.5.1, wxWidgets has the ability to be built as
@@ -468,7 +467,7 @@ COMPILER_PREFIX=<string>
If you build with multiple versions of the same compiler, you can put
their outputs into directories like "vc6_lib", "vc8_lib" etc. instead of
"vc_lib" by setting this variable to e.g. "vc6". This is merely a
convenience variable, you can achieve the same effect (but different
convenience variable, you can achieve the same effect (but different
directory names) with the CFG option.
CFLAGS

11
docs/osx/readme.txt
View File

@@ -2,23 +2,22 @@ Welcome to wxWidgets/Mac
More Information is available from the wxWidgets project home page at
http://www.wxwidgets.org
https://www.wxwidgets.org
For more information, please see install.txt, todo.txt, and the
manuals.
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from the wxWidgets.org homepage.
Questions/Problems related directly to the mac port can be sent directly
csomor@advancedconcepts.ch.
wxWidgets/Mac doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
wxWidgets/Mac doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
claim to be suitable for any special or general purpose.
Regards,
Stefan Csomor

26
docs/qt/readme.txt
View File

@@ -4,15 +4,15 @@
You have downloaded the Qt port of the wxWidgets GUI library.
It is required to use at least Qt 5 and some features are
only available when using Qt 5.2 or higher.
only available when using Qt 5.2 or higher.
More info about the wxWidgets project (including all the
other ports and version of wxWidgets) can be found at the
main wxWidgets homepage at:
http://www.wxwidgets.org/
Information on how to install can be found in the file
https://www.wxwidgets.org/
Information on how to install can be found in the file
INSTALL.txt, but if you cannot wait, this should work on
many systems:
@@ -30,23 +30,21 @@ different builds of it (for example with and without debug) in
parallel. If you build in the source directory, don't forget to
do "make clean" before changing the configuration!
When you run into problems, please read the INSTALL.txt and
When you run into problems, please read the INSTALL.txt and
follow those instructions. If you still don't have any success,
please send a bug report to one of our mailing list, INCLUDING
A DESCRIPTION OF YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR
VERSION OF GTK, WXGTK, WHAT DISTRIBUTION YOU USE AND WHAT ERROR
please send a bug report to one of our mailing list, INCLUDING
A DESCRIPTION OF YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR
VERSION OF GTK, WXGTK, WHAT DISTRIBUTION YOU USE AND WHAT ERROR
WAS REPORTED. I know this has no effect, but I tried...
Please send problems concerning installation, feature requests,
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. These can
be found at http://www.wxwidgets.org and more specifically at
http://lists.wxwidgets.org.
be found at https://www.wxwidgets.org/support/mailing-lists/
wxWidgets doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
wxWidgets doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
claim to be suitable for any special or general purpose.
Regards,
The wxWidgets Team

24
docs/readme.txt
View File

@@ -5,7 +5,6 @@ Welcome to the latest development release of wxWidgets, a free and
open source cross-platform C++ framework for writing advanced GUI
applications using native controls.
wxWidgets allows you to write native-looking GUI applications for
all the major desktop platforms and also helps with abstracting
the differences in the non-GUI aspects between them. It is free
@@ -14,27 +13,21 @@ with the full, easy to read and modify, source and extensive
documentation and a collection of more than a hundred examples.
You can learn more about wxWidgets at
http://www.wxwidgets.org/
https://www.wxwidgets.org/
and read its documentation online at
http://docs.wxwidgets.org/3.1.0/
http://docs.wxwidgets.org/3.1.0/
wxWidgets sources and binaries for the selected platforms are
available for download from
https://sourceforge.net/projects/wxwindows/files/3.1.0/
or
ftp://ftp.wxwidgets.org/pub/3.1.0/
https://github.com/wxWidgets/wxWidgets/releases/tag/v3.1.0/
Please see the "Files" section below for the description of various
files available at these locations.
Changes in this release
-----------------------
@@ -167,11 +160,12 @@ Further information
If you are looking for support, you can get it from
- wxForum at http://forums.wxwidgets.org/
- wx-users mailing list (http://www.wxwidgets.org/support/mailing-lists/)
- #wxwidgets IRC channel
- http://stackoverflow.com/ if you tag your question with "wxwidgets"
- Mailing Lists: https://www.wxwidgets.org/support/mailing-lists/
- Discussion Forums: https://forums.wxwidgets.org/
- #wxwidgets IRC Channel: https://www.wxwidgets.org/support/irc/
- Stack Overflow (tag your questions with "wxwidgets"):
https://stackoverflow.com/questions/tagged/wxwidgets
- Please report bugs at http://trac.wxwidgets.org/newticket
Have fun!

19
docs/univ/readme.txt
View File

@@ -11,11 +11,7 @@ Tom Ryan!
---------------
wxUniversal is a port of wxWidgets which implements the various GUI controls
by drawing them itself (using low level wxWidgets classes). Please see
http://www.wxwidgets.org/wxuniv.htm
for more details about it.
by drawing them itself (using low level wxWidgets classes).
The advantage of wxUniversal is that you have precise control over the
controls' appearance (it is not always possible to change all aspects of the
@@ -50,7 +46,7 @@ to include/wx/univ/setup.h before following these steps.
a) Using Visual C++ 6.0/7.x
Follow wxMSW instructions but make sure to choose one of the "Universal"
Follow wxMSW instructions but make sure to choose one of the "Universal"
configurations before building.
b) Cygwin
@@ -64,7 +60,7 @@ b) Cygwin
** the instructions may be out of date as for wxWidgets 2.5.2+ **
c) Other compilers
Borland:
Borland:
in the wxwindows\src\msw directory run
'make -f makefile.b32 WXUSINGUNIV=1' to build the library and then run
'make -f makefile.b32 WXUSINGUNIV=1' in the sample directory which you wish
@@ -127,12 +123,8 @@ documentation instead.
Support for wxUniversal is available from the same places as for wxWidgets
itself, namely:
* Usenet newsgroup comp.soft-sys.wxwindows
* Mailing lists: see http://lists.wxwindows.org/ for more information
* WWW page: http://www.wxwidgets.org/
* Website: https://www.wxwidgets.org/
* Mailing Lists: https://www.wxwidgets.org/support/mailing-lists/
Hope you find wxUniversal useful!
@@ -141,4 +133,3 @@ itself, namely:
This file is accurate for the version 2.3.4 of wxUniversal. It was last
modified on Apr 15, 2002.

136
docs/x11/install.txt
View File

@@ -9,8 +9,8 @@ IMPORTANT NOTE:
mailing wxwin-users or the author. Preferably, try to fix the
problem first and then send a patch to the author.
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
example: wxX11 2.8.0, gcc 2.95.4, Redhat 6.2
First steps
@@ -32,7 +32,7 @@ First steps
Using configure is the recommended way to build the library. If it doesn't
work for you for whatever reason, please report it (together with detailed
information about your platform and the (relevant part of) contents of
config.log file) to wx-dev@lists.wxwidgets.org.
config.log file).
COMPILING USING CONFIGURE
=========================
@@ -40,7 +40,7 @@ COMPILING USING CONFIGURE
* The simplest case
-------------------
If you compile wxWidgets on Linux for the first time and don't like to read
If you compile wxWidgets on Linux for the first time and don't like to read
install instructions just do (in the base dir):
> ./configure --with-x11
@@ -68,16 +68,16 @@ If you want to remove wxWidgets on Unix you can do this:
* The expert case
-----------------
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and X11, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and X11, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
of wxWidgets - you may also want to create different versions of wxWidgets
and test them concurrently. Most typically, this would be a version configured
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can
currently be installed, so you'd have to use local version of the library for
that purpose.
For building three versions (one GTK, one X11 and a debug version of the GTK
For building three versions (one GTK, one X11 and a debug version of the GTK
source) you'd do this:
md buildx11
@@ -125,20 +125,20 @@ g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo
The Unix variants of wxWidgets use GNU configure. If you have problems with
your make use GNU make instead.
If you have general problems with installation, see the wxWidgets website at
If you have general problems with installation, see the wxWidgets website at
http://www.wxwidgets.org/
for newest information. If you still don't have any success, please send a bug
report to one of our mailing lists (see my homepage) INCLUDING A DESCRIPTION OF
YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR VERSION OF X, WHAT DISTRIBUTION
https://www.wxwidgets.org/
for newest information. If you still don't have any success, please send a bug
report to one of our mailing lists (see my homepage) INCLUDING A DESCRIPTION OF
YOUR SYSTEM AND YOUR PROBLEM, SUCH AS YOUR VERSION OF X, WHAT DISTRIBUTION
YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect, but I tried...
* GUI libraries
---------------
wxWidgets/X11 requires the X11 library to be installed on your system.
* Additional libraries
----------------------
@@ -148,7 +148,7 @@ Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
many aspects. As of writing this, virtually all Linux distributions have
+correct glibc 2 support.
You can disable thread support by running
You can disable thread support by running
./configure --disable-threads
make
@@ -156,7 +156,7 @@ su <type root password>
make install
ldconfig
exit
* Building wxX11 on OS/2
------------------------
@@ -187,7 +187,7 @@ SET MAKESHELL=ash
Be warned that depending on the precise version of your make, the
variable that needs to be set might be MAKE_SHELL instead of MAKESHELL.
If you have a really deficient version of GNU make, it might even be
necessary to set SHELL or even COMSPEC to a unix like shell as well.
necessary to set SHELL or even COMSPEC to a unix like shell as well.
Notice that the delivered configure scripts are fully OS/2 aware, so you
can simply run
@@ -203,16 +203,16 @@ explicitly set CFLAGS prior to running configure.
-----------------------
Using the SGI native compilers, it is recommended that you
also set CFLAGS and CXXFLAGS before running configure. These
also set CFLAGS and CXXFLAGS before running configure. These
should be set to :
CFLAGS="-mips3 -n32"
CFLAGS="-mips3 -n32"
CXXFLAGS="-mips3 -n32"
This is essential if you want to use the resultant binaries
on any other machine than the one it was compiled on. If you
have a 64bit machine (Octane) you should also do this to ensure
you don't accidently build the libraries as 64bit (which is
This is essential if you want to use the resultant binaries
on any other machine than the one it was compiled on. If you
have a 64bit machine (Octane) you should also do this to ensure
you don't accidently build the libraries as 64bit (which is
untested).
The SGI native compiler support has only been tested on Irix 6.5.
@@ -249,16 +249,16 @@ to see all the options please use:
./configure --help
The basic philosophy is that if you want to use different
configurations, like a debug and a release version,
configurations, like a debug and a release version,
or use the same source tree on different systems,
you have only to change the environment variable OSTYPE.
(Sadly this variable is not set by default on some systems
in some shells - on SGI's for example). So you will have to
set it there. This variable HAS to be set before starting
configure, so that it knows which system it tries to
in some shells - on SGI's for example). So you will have to
set it there. This variable HAS to be set before starting
configure, so that it knows which system it tries to
configure for.
Configure will complain if the system variable OSTYPE has
Configure will complain if the system variable OSTYPE has
not been defined. And Make in some circumstances as well...
@@ -292,33 +292,33 @@ The following options handle the kind of library you want to build.
such as Sun with gcc 2.8.X which
would otherwise produce segvs.
--enable-profile Add profiling info to the object
--enable-profile Add profiling info to the object
files. Currently broken, I think.
--enable-no_rtti Enable compilation without creation of
C++ RTTI information in object files.
This will speed-up compilation and reduce
C++ RTTI information in object files.
This will speed-up compilation and reduce
binary size.
--enable-no_exceptions Enable compilation without creation of
C++ exception information in object files.
This will speed-up compilation and reduce
C++ exception information in object files.
This will speed-up compilation and reduce
binary size. Also fewer crashes during the
actual compilation...
--enable-no_deps Enable compilation without creation of
dependency information.
--enable-permissive Enable compilation without checking for strict
ANSI conformance. Useful to prevent the build
dying with errors as soon as you compile with
Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
--enable-mem_tracing Add built-in memory tracing.
--enable-dmalloc Use the dmalloc memory debugger.
Read more at www.letters.com/dmalloc/
--enable-debug_info Add debug info to object files and
executables for use with debuggers
such as gdb (or its many frontends).
@@ -328,7 +328,7 @@ The following options handle the kind of library you want to build.
useful internal debugging tricks (such
as automatically reporting illegal calls)
to work. Note that program and library
must be compiled with the same debug
must be compiled with the same debug
options.
* Feature Options
@@ -339,44 +339,44 @@ in wxWidgets snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxX11
you'll be surprised at its immense size. This can sometimes be
drastically reduced by removing features from wxWidgets that
drastically reduced by removing features from wxWidgets that
are not used in your program. The most relevant such features
are
--without-libpng Disables PNG image format code.
--without-libjpeg Disables JPEG image format code.
{ --without-odbc Disables ODBC code. Not yet. }
--without-expat Disable XML classes based on Expat parser.
--disable-resources Disables the use of *.wxr type
resources.
--disable-threads Disables threads. Will also
disable sockets.
--disable-sockets Disables sockets.
--disable-dnd Disables Drag'n'Drop.
--disable-clipboard Disables Clipboard.
--disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
--disable-file Disables the wxFile class.
--disable-textfile Disables the wxTextFile class.
--disable-intl Disables the internationalisation.
--disable-validators Disables validators.
--disable-accel Disables accel.
Apart from disabling certain features you can very often "strip"
the program of its debugging information resulting in a significant
reduction in size.
@@ -391,13 +391,13 @@ of all configurable options.
The following must be done in the base directory (e.g. ~/wxX11
or whatever)
Now the makefiles are created (by configure) and you can compile
Now the makefiles are created (by configure) and you can compile
the library by typing:
make
make yourself some coffee, as it will take some time. On an old
386SX possibly two weeks. During compilation, you'll get a few
386SX possibly two weeks. During compilation, you'll get a few
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
@@ -408,12 +408,12 @@ Then you may install the library and its header files under
have to log in as root (i.e. run "su" and enter the root
password) and type
make install
make install
You can remove any traces of wxWidgets by typing
make uninstall
If you want to save disk space by removing unnecessary
object-files:
@@ -435,12 +435,12 @@ like this
CXX = g++
minimal: minimal.o
$(CXX) -o minimal minimal.o `wx-config --libs`
$(CXX) -o minimal minimal.o `wx-config --libs`
minimal.o: minimal.cpp
$(CXX) `wx-config --cxxflags` -c minimal.cpp -o minimal.o
clean:
clean:
rm -f *.o minimal
This is certain to become the standard way unless we decide
@@ -452,7 +452,7 @@ specify required libraries when running wx-config. For example,
with libraries required by core GUI classes and wxHTML classes. See
the manual for more information on the libraries.
2) The other way creates a project within the source code
2) The other way creates a project within the source code
directories of wxWidgets. For this endeavour, you'll need
GNU autoconf version 2.14 and add an entry to your Makefile.in
to the bottom of the configure.in script and run autoconf
@@ -518,8 +518,6 @@ Bug reports
-----------
Please send bug reports with a description of your environment,
compiler and the error message(s) to the wxwin-developers mailing list at:
wx-dev@lists.wxwidgets.org
compiler and the error message(s) to the developers mailing list at:
https://www.wxwidgets.org/support/mailing-lists/

15
docs/x11/readme.txt
View File

@@ -9,9 +9,9 @@ intention is to have it run on NanoX as well as desktop X11.
More information about the wxWidgets project as a whole
can be found at:
http://www.wxwidgets.org
Information on how to install can be found in the file
https://www.wxwidgets.org
Information on how to install can be found in the file
install.txt, but if you cannot wait, this should work on
many systems:
@@ -31,17 +31,17 @@ YOUR PROBLEM, SUCH AS YOUR VERSION OF X, WHAT DISTRIBUTION YOU USE
AND WHAT ERROR WAS REPORTED. Alternatively, you may also use the bug
reporting system linked from the wxWidgets web page.
The library produced by the install process will be called
The library produced by the install process will be called
libwx_x11univ[d].a (static) and libwx_x11univ[d]-2.3.so.0.0.0
(shared) so that once a binary incompatible version of
wxWidgets/X11 comes out we'll augment the library version number
to avoid linking problems.
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from www.wxwidgets.org.
wxWidgets/X11 doesn't come with any guarantee whatsoever. It might
wxWidgets/X11 doesn't come with any guarantee whatsoever. It might
crash your hard disk or destroy your monitor. It doesn't claim to be
suitable for any special or general purpose.
@@ -67,4 +67,3 @@ Some remaining issues:
Regards,
The wxWidgets team

8
include/wx/defs.h
View File

@@ -154,10 +154,10 @@
/*
Clang Support
*/
#ifndef WX_HAS_CLANG_FEATURE
# ifndef __has_feature
# define WX_HAS_CLANG_FEATURE(x) 0
# ifndef __has_feature
# define WX_HAS_CLANG_FEATURE(x) 0
# else
# define WX_HAS_CLANG_FEATURE(x) __has_feature(x)
# endif
@@ -1261,7 +1261,7 @@ typedef wxUint32 wxDword;
#else
/*
This should never happen for the current architectures but if you're
using one where it does, please contact wx-dev@lists.wxwidgets.org.
using one where it does, please contact wx-dev@googlegroups.com.
*/
#error "Pointers can't be stored inside integer types."
#endif

4
include/wx/longlong.h
View File

@@ -45,12 +45,12 @@
#warning "Your compiler does not appear to support 64 bit "\
"integers, using emulation class instead.\n" \
"Please report your compiler version to " \
"wx-dev@lists.wxwidgets.org!"
"wx-dev@googlegroups.com!"
#else
#pragma warning "Your compiler does not appear to support 64 bit "\
"integers, using emulation class instead.\n" \
"Please report your compiler version to " \
"wx-dev@lists.wxwidgets.org!"
"wx-dev@googlegroups.com!"
#endif
#define wxUSE_LONGLONG_WX 1

2
include/wx/osx/config_xcode.h
View File

@@ -122,7 +122,7 @@
#define HAVE_LOCALE_T 1
#define wxHAS_KQUEUE 1
#define PACKAGE_BUGREPORT "wx-dev@lists.wxwidgets.org"
#define PACKAGE_BUGREPORT "wx-dev@googlegroups.com"
#define PACKAGE_NAME "wxWidgets"
#define PACKAGE_STRING "wxWidgets 3.1.0"
#define PACKAGE_TARNAME "wxwidgets"

2
interface/wx/mediactrl.h
View File

@@ -226,7 +226,7 @@ public:
The only real tricky part is that you need to make sure the file in compiled in,
which if there are just backends in there will not happen and you may need to
use a force link hack (see http://www.wxwidgets.org/wiki/index.php/RTTI).
use a force link hack (see https://wiki.wxwidgets.org/RTTI).
This is a rather simple example of how to create a backend in the
wxActiveXContainer documentation.

2
locale/it.po
View File

@@ -5,7 +5,7 @@ msgstr ""
"POT-Creation-Date: 2015-05-23 22:46+0400\n"
"PO-Revision-Date: 2015-07-09 11:22+0200\n"
"Last-Translator: bovirus <@bovirus@gmail.com>\n"
"Language-Team: wxWidgets translators <wx-translators@lists.wxwidgets.org>\n"
"Language-Team: wxWidgets translators <wx-translators@googlegroups.com>\n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"

2
locale/msw/it.po
View File

@@ -7,7 +7,7 @@ msgstr ""
"POT-Creation-Date: 2006-10-29 14:59+0100\n"
"PO-Revision-Date: 2005-08-12 14:23:42+0100\n"
"Last-Translator: Mike Wetherell <mike.wetherell@ntlworld.com>\n"
"Language-Team: wxWidgets translators <wx-translators@lists.wxwidgets.org>\n"
"Language-Team: wxWidgets translators <wx-translators@googlegroups.com>\n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"

2
samples/internat/it/internat.po
View File

@@ -9,7 +9,7 @@ msgstr ""
"POT-Creation-Date: 2009-02-08 16:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Francesco Montorsi <f18m_cpp217828@yahoo.it>\n"
"Language-Team: wxWidgets translators <wx-translators@lists.wxwidgets.org>\n"
"Language-Team: wxWidgets translators <wx-translators@googlegroups.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

10
samples/internat/readme.txt
View File

@@ -93,11 +93,5 @@ A. For Unix, you should be able to get the source distribution of any GNU mirror
Q. What's i18n?
A. Count the number of letters in the word "internationalization".
Q. Where to send comments,
additional translations,
flames,
money?
A. To Vadim Zeitlin <zeitlin@dptmaths.ens-cachan.fr>,
wxWidgets list <wx-dev@lists.wxwidgets.org>,
/dev/null (platform-dependent),
wxWidgets dev team Swiss bank account.
Q. Where to send comments, or additional translations?
A. wxWidgets mailing list <wx-dev@googlegroups.com>.

4
samples/internat/sv/internat.po
View File

@@ -4,11 +4,11 @@
msgid ""
msgstr ""
"Project-Id-Version: wxWidgets 2.6 internat sample\n"
"Report-Msgid-Bugs-To: wxDevelopers <wx-dev@lists.wxwidgets.org>\n"
"Report-Msgid-Bugs-To: wxDevelopers <wx-dev@googlegroups.com>\n"
"POT-Creation-Date: 2005-06-02 13:21+0200\n"
"PO-Revision-Date: 2005-06-02 13:45+0200\n"
"Last-Translator: Jonas Rydberg <jonas@arbor.se>\n"
"Language-Team: wxWidgets translators <wx-translators@lists.wxwidgets.org>\n"
"Language-Team: wxWidgets translators <wx-translators@googlegroups.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"