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

applied typos and spelling error fixes patch from Olly Betts

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15779 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2002-06-07 20:15:28 +00:00
parent f06ef5f4a3
commit 2edb0bdef6
158 changed files with 429 additions and 422 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/x11/install.txt
View File

@@ -70,7 +70,7 @@ If you want to remove wxWindows on Unix you can do this:
If you want to do some more serious cross-platform programming with wxWindows,
such as for GTK and X11, you can now build two complete libraries and use
them concurretly. For this end, you have to create a directory for each build
them concurrently. For this end, you have to create a directory for each build
of wxWindows - you may also want to create different versions of wxWindows
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
@@ -101,7 +101,7 @@ cd ..
You get errors during compilation: The reason is that you probably have a broken
compiler, which includes almost everything that is called gcc. If you use gcc 2.8
you have to disable optimsation as the compiler will give up with an internal
you have to disable optimisation as the compiler will give up with an internal
compiler error.
If there is just any way for you to use egcs, use egcs. We cannot fix gcc.
@@ -269,11 +269,11 @@ Given below are the commands to change the default behaviour,
i.e. if it says "--disable-threads" it means that threads
are enabled by default.
Many of the confiugre options have been thoroughly tested
Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
You have to add --with-x11 on platforms, where X11 is
not the default (on Linux, configure will deafult to GTK).
not the default (on Linux, configure will default to GTK).
--without-gtk Don't use the GIMP ToolKit (GTK).
@@ -312,9 +312,10 @@ The following options handle the kind of library you want to build.
--enable-no_deps Enable compilation without creation of
dependency information.
--enable-permissive Enable compilation without creation of
giving erros as soon as you compile with
Solaris ANSI-defying headers...
--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.
@@ -336,7 +337,7 @@ The following options handle the kind of library you want to build.
* Feature Options
-------------------
Many of the confiugre options have been thoroughly tested
Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
@@ -363,7 +364,7 @@ are
--disable-clipboard Disables Clipboard.
--disable-serial Disables object instance serialiasation.
--disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
@@ -397,9 +398,9 @@ make yourself some coffee, as it will take some time. On an old
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
directiry and type "make" there.
directory and type "make" there.
Then you may install the library and it's header files under
Then you may install the library and its header files under
/usr/local/include/wx and /usr/local/lib respectively. You
have to log in as root (i.e. run "su" and enter the root
password) and type
@@ -440,7 +441,7 @@ clean:
rm -f *.o minimal
This is certain to become the standard way unless we decide
to sitch to tmake.
to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need