typos and other doc corrections from Olly Betts (patch 573738)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@16016 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -282,7 +282,7 @@ MANY bugfixes.
|
|||||||
|
|
||||||
*** 22th March 2000: wxWindows 2.1.15 released ***
|
*** 22th March 2000: wxWindows 2.1.15 released ***
|
||||||
|
|
||||||
Build fix. RPMs no loner require GTK's include files.
|
Build fix. RPMs no longer require GTK's include files.
|
||||||
|
|
||||||
An extra library for the OpenGl class now gets built
|
An extra library for the OpenGl class now gets built
|
||||||
*** 19th March 2000: wxWindows 2.1.14 released ***
|
*** 19th March 2000: wxWindows 2.1.14 released ***
|
||||||
|
@@ -207,7 +207,7 @@ often faced with an original string which is not as informative as
|
|||||||
it normally should be, being succinct, cryptic, or otherwise ambiguous.
|
it normally should be, being succinct, cryptic, or otherwise ambiguous.
|
||||||
Before choosing how to translate the string, she needs to understand
|
Before choosing how to translate the string, she needs to understand
|
||||||
better what the string really means and how tight the translation has
|
better what the string really means and how tight the translation has
|
||||||
to be. Most of times, when problems arise, the only way left to make
|
to be. Most of the time, when problems arise, the only way left to make
|
||||||
her judgment is looking at the true program sources from where this
|
her judgment is looking at the true program sources from where this
|
||||||
string originated, searching for surrounding comments the programmer
|
string originated, searching for surrounding comments the programmer
|
||||||
might have put in there, and looking around for helping clues of
|
might have put in there, and looking around for helping clues of
|
||||||
@@ -223,7 +223,7 @@ It is most probable that she will still be able to find some of the
|
|||||||
hints she needs. She will learn quickly to not feel uncomfortable
|
hints she needs. She will learn quickly to not feel uncomfortable
|
||||||
in program code, paying more attention to programmer's comments,
|
in program code, paying more attention to programmer's comments,
|
||||||
variable and function names (if he dared choosing them well), and
|
variable and function names (if he dared choosing them well), and
|
||||||
overall organization, than to programmation itself.
|
overall organization, than to the program code itself.
|
||||||
|
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
|
@@ -342,7 +342,7 @@ mouse events or all mouse events.}
|
|||||||
\wxhelpref{wxScrollBar}{wxscrollbar}, \wxhelpref{wxSlider}{wxslider},and \wxhelpref{wxSpinButton}{wxspinbutton}.}
|
\wxhelpref{wxScrollBar}{wxscrollbar}, \wxhelpref{wxSlider}{wxslider},and \wxhelpref{wxSpinButton}{wxspinbutton}.}
|
||||||
\twocolitem{\wxhelpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
|
\twocolitem{\wxhelpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
|
||||||
\twocolitem{\wxhelpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
|
\twocolitem{\wxhelpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
|
||||||
and EVT\_SPLITTER\_DOUBLECLICKED macros are used to handle the various splitter window events.}
|
and EVT\_SPLITTER\_DCLICK macros are used to handle the various splitter window events.}
|
||||||
\twocolitem{\wxhelpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
|
\twocolitem{\wxhelpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
|
||||||
events informing the application that the user has changed the system colours (Windows only).}
|
events informing the application that the user has changed the system colours (Windows only).}
|
||||||
\twocolitem{\wxhelpref{wxTreeEvent}{wxtreeevent}}{These macros handle \wxhelpref{wxTreeCtrl}{wxtreectrl} events.}
|
\twocolitem{\wxhelpref{wxTreeEvent}{wxtreeevent}}{These macros handle \wxhelpref{wxTreeCtrl}{wxtreectrl} events.}
|
||||||
|
@@ -38,7 +38,7 @@ Processes a wxEVT\_COMMAND\_SPLITTER\_SASH\_POS\_CHANGED event.}
|
|||||||
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
|
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
|
||||||
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event. This event can't
|
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event. This event can't
|
||||||
be vetoed.}
|
be vetoed.}
|
||||||
\twocolitem{{\bf EVT\_SPLITTER\_DOUBLECLICKED(id, func)}}{The sash was double
|
\twocolitem{{\bf EVT\_SPLITTER\_DCLICK(id, func)}}{The sash was double
|
||||||
clicked. The default behaviour is to unsplit the window when this happens
|
clicked. The default behaviour is to unsplit the window when this happens
|
||||||
(unless the minimum pane size has been set to a value greater than zero). This
|
(unless the minimum pane size has been set to a value greater than zero). This
|
||||||
won't happen if you veto this event. Processes a
|
won't happen if you veto this event. Processes a
|
||||||
|
@@ -55,7 +55,7 @@ it is set, or to prevent the change from taking place.
|
|||||||
Processes a wxEVT\_COMMAND\_SPLITTER\_SASH\_POS\_CHANGED event.}
|
Processes a wxEVT\_COMMAND\_SPLITTER\_SASH\_POS\_CHANGED event.}
|
||||||
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
|
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
|
||||||
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event.}
|
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event.}
|
||||||
\twocolitem{{\bf EVT\_SPLITTER\_DOUBLECLICKED(id, func)}}{The sash was double
|
\twocolitem{{\bf EVT\_SPLITTER\_DCLICK(id, func)}}{The sash was double
|
||||||
clicked. The default behaviour is to unsplit the window when this happens
|
clicked. The default behaviour is to unsplit the window when this happens
|
||||||
(unless the minimum pane size has been set to a value greater than zero).
|
(unless the minimum pane size has been set to a value greater than zero).
|
||||||
Processes a wxEVT\_COMMAND\_SPLITTER\_DOUBLECLICKED event.}
|
Processes a wxEVT\_COMMAND\_SPLITTER\_DOUBLECLICKED event.}
|
||||||
|
@@ -363,7 +363,7 @@ mouse events or all mouse events.}
|
|||||||
\helpref{wxScrollBar}{wxscrollbar}, \helpref{wxSlider}{wxslider},and \helpref{wxSpinButton}{wxspinbutton}.}
|
\helpref{wxScrollBar}{wxscrollbar}, \helpref{wxSlider}{wxslider},and \helpref{wxSpinButton}{wxspinbutton}.}
|
||||||
\twocolitem{\helpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
|
\twocolitem{\helpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
|
||||||
\twocolitem{\helpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
|
\twocolitem{\helpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
|
||||||
and EVT\_SPLITTER\_DOUBLECLICKED macros are used to handle the various splitter window events.}
|
and EVT\_SPLITTER\_DCLICK macros are used to handle the various splitter window events.}
|
||||||
\twocolitem{\helpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
|
\twocolitem{\helpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
|
||||||
events informing the application that the user has changed the system colours (Windows only).}
|
events informing the application that the user has changed the system colours (Windows only).}
|
||||||
\twocolitem{\helpref{wxTreeEvent}{wxtreeevent}}{These macros handle \helpref{wxTreeCtrl}{wxtreectrl} events.}
|
\twocolitem{\helpref{wxTreeEvent}{wxtreeevent}}{These macros handle \helpref{wxTreeCtrl}{wxtreectrl} events.}
|
||||||
|
@@ -8,17 +8,18 @@ First of all, here is what you will need:
|
|||||||
1. GNU gettext package version 0.10.35 or later (NB: earlier versions were
|
1. GNU gettext package version 0.10.35 or later (NB: earlier versions were
|
||||||
known to have serious bugs)
|
known to have serious bugs)
|
||||||
|
|
||||||
a) for Unix systems you can download gettext-0.10.tar.gz from any of GNU
|
a) for Unix systems you can download gettext-0.10.tar.gz from any GNU
|
||||||
mirrors (RPMs and DEBs are also available from the usual places)
|
mirror (RPMs and DEBs are also available from the usual places)
|
||||||
|
|
||||||
b) for Windows you can grab the precompiled binaries from www.wxwindows.org
|
b) for Windows you can download the precompiled binaries from
|
||||||
|
www.wxwindows.org
|
||||||
|
|
||||||
2. A way to run a program recursively on an entire directory from the command
|
2. A way to run a program recursively on an entire directory from the command
|
||||||
line:
|
line:
|
||||||
|
|
||||||
a) for Unix systems, this is done in locale/Makefile using standard find
|
a) for Unix systems, this is done in locale/Makefile using the standard find
|
||||||
command and xargs which is installed on almost all modern Unices, if you
|
command and xargs which is installed on almost all modern Unices. If you
|
||||||
are unhappy enough to not have it you can use -exec option of find
|
are unlucky enough to not have xargs, you can use the -exec option of find
|
||||||
instead.
|
instead.
|
||||||
|
|
||||||
b) for Win32 systems this is less trivial: if you have 4DOS/4NT/bash, that's
|
b) for Win32 systems this is less trivial: if you have 4DOS/4NT/bash, that's
|
||||||
@@ -35,7 +36,7 @@ gettext documentation for more details). It happens in several steps:
|
|||||||
1. the strings to translate are extracted from the C++ sources using xgettext
|
1. the strings to translate are extracted from the C++ sources using xgettext
|
||||||
program into a wxstd.po file which is a "text message catalog"
|
program into a wxstd.po file which is a "text message catalog"
|
||||||
|
|
||||||
2. this new wxtd.po file (recreated each one some new text messages are added
|
2. this new wxstd.po file (recreated each time some new text messages are added
|
||||||
to wxWindows) is merged with existing translations in another .po file (for
|
to wxWindows) is merged with existing translations in another .po file (for
|
||||||
example, de.po) and replaces this file (this is done using the program
|
example, de.po) and replaces this file (this is done using the program
|
||||||
msgmerge)
|
msgmerge)
|
||||||
@@ -45,11 +46,11 @@ gettext documentation for more details). It happens in several steps:
|
|||||||
4. finally, msgformat must be run to produce a .mo file: "binary message catalog"
|
4. finally, msgformat must be run to produce a .mo file: "binary message catalog"
|
||||||
|
|
||||||
|
|
||||||
How does it happen in practice? Under Unix there is a Makefile under "locale"
|
How does it happen in practice? Under Unix there is a Makefile in the "locale"
|
||||||
directory which will do almost everything (except translations) for you, i.e.
|
directory which will do almost everything (except translations) for you, i.e.
|
||||||
just type "make lang.po" to create or update the message catalog for 'lang'.
|
just type "make lang.po" to create or update the message catalog for 'lang'.
|
||||||
Then edit the resulting lang.po and make sure that there are no empty or fuzzy
|
Then edit the resulting lang.po and make sure that there are no empty or fuzzy
|
||||||
translations left (empty translations are the one with msgstr "", fuzzy
|
translations left (empty translations are the ones with msgstr "", fuzzy
|
||||||
translations are those which have the word "fuzzy" in a comment just above
|
translations are those which have the word "fuzzy" in a comment just above
|
||||||
them). Then type "make lang.mo" which will create the binary message catalog.
|
them). Then type "make lang.mo" which will create the binary message catalog.
|
||||||
|
|
||||||
@@ -62,6 +63,9 @@ Author: VZ
|
|||||||
Version: $Id$
|
Version: $Id$
|
||||||
|
|
||||||
$Log$
|
$Log$
|
||||||
|
Revision 1.2 2002/07/03 15:01:26 VZ
|
||||||
|
typos and other doc corrections from Olly Betts (patch 573738)
|
||||||
|
|
||||||
Revision 1.1 2000/03/07 10:53:53 VZ
|
Revision 1.1 2000/03/07 10:53:53 VZ
|
||||||
technote about translations added
|
technote about translations added
|
||||||
|
|
||||||
|
@@ -14,7 +14,7 @@ If adding to the existing manual in docs/latex/wx, you need to
|
|||||||
create a new .tex file, e.g. myclass.tex, and add it to the
|
create a new .tex file, e.g. myclass.tex, and add it to the
|
||||||
list of classes in classes.tex (in strict alphabetical order).
|
list of classes in classes.tex (in strict alphabetical order).
|
||||||
You may also want to write a separate topic file, e.g. tmyclass.tex,
|
You may also want to write a separate topic file, e.g. tmyclass.tex,
|
||||||
and add the entry to topics.tex. Also, if applicable, and an entry
|
and add the entry to topics.tex. If applicable, also add an entry
|
||||||
to category.tex.
|
to category.tex.
|
||||||
|
|
||||||
If compiling a separate manual, copy an existing set of files from the
|
If compiling a separate manual, copy an existing set of files from the
|
||||||
|
@@ -15,10 +15,11 @@ This document is available online <a href="http://biolpc22.york.ac.uk/wx/bc/ide.
|
|||||||
|
|
||||||
<h2>
|
<h2>
|
||||||
Before you begin</h2>
|
Before you begin</h2>
|
||||||
This refers to the 2.1.15 wxWindows distribution. It is my account of trying
|
This refers to the <b>2.1.16</b> and 2.1.15 wxWindows distribution. It
|
||||||
to compile the samples so I can use the Borland IDE to edit/compile/debug.
|
is my account of trying to compile the samples so I can use the Borland
|
||||||
I have used CBuilder 1.00 (2 patches, nice and fast) CBuilder 3 (slower)
|
IDE to edit/compile/debug. I have used CBuilder 1.00 (2 patches, nice and
|
||||||
and CBuilder 4 (only occasionally)
|
fast), CBuilder 3 (slower), and CBuilder 4 (more recently).
|
||||||
|
|
||||||
<p>Make sure that the wx distribution is extracted to a path with no spaces
|
<p>Make sure that the wx distribution is extracted to a path with no spaces
|
||||||
in it, and preferably on the root of your drive. Borland's compilers sometimes
|
in it, and preferably on the root of your drive. Borland's compilers sometimes
|
||||||
have problems with spaces and with the long paths which occur if you try
|
have problems with spaces and with the long paths which occur if you try
|
||||||
@@ -30,15 +31,15 @@ Build the <b>wx\wx32.lib</b> and related files using the command line compiler
|
|||||||
<p><tt>set wxwin=pathtowx</tt>
|
<p><tt>set wxwin=pathtowx</tt>
|
||||||
<br><tt>set bccdir=pathtobc4</tt>
|
<br><tt>set bccdir=pathtobc4</tt>
|
||||||
<br><tt>make -f makefile.b32</tt>
|
<br><tt>make -f makefile.b32</tt>
|
||||||
<p>In my case this I extracted the wx distribution in <b>c:\ </b>and the
|
<p>In my case this I extracted the wx distribution in <b>c:\</b> and the
|
||||||
compiler is in <b>w:\borland\cb\bin </b>so this looks:
|
compiler is in <b>w:\borland\cb\bin</b> so this looks:
|
||||||
<p><tt>set wxwin=c:\wx</tt>
|
<p><tt>set wxwin=c:\wx</tt>
|
||||||
<br><tt>set bccdir=w:\borland\cb</tt>
|
<br><tt>set bccdir=w:\borland\cb</tt>
|
||||||
<br><tt>make -f makefile.b32</tt>
|
<br><tt>make -f makefile.b32</tt>
|
||||||
<p>If this doesn't <b>compile</b>,
|
<p>If this doesn't <b>compile</b>,
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
you've probably got the <b><tt>set wxwin </tt></b>command wrong,</li>
|
you've probably got the <b><tt>set wxwin</tt></b> command wrong,</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
or the path was not set by the Borland setup</li>
|
or the path was not set by the Borland setup</li>
|
||||||
@@ -46,7 +47,7 @@ or the path was not set by the Borland setup</li>
|
|||||||
If this doesn't <b>link</b>,
|
If this doesn't <b>link</b>,
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
you've probably got the <b><tt>set bccdir </tt></b>command wrong</li>
|
you've probably got the <b><tt>set bccdir</tt></b> command wrong</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<hr WIDTH="100%">
|
<hr WIDTH="100%">
|
||||||
@@ -56,18 +57,17 @@ To make the samples</h2>
|
|||||||
<h3>
|
<h3>
|
||||||
Solution 1</h3>
|
Solution 1</h3>
|
||||||
|
|
||||||
<h4>
|
|
||||||
<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modified
|
<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modified
|
||||||
cpp, mak and bpr files - it will overwrite your wx distribution cpp files!</h4>
|
cpp, mak and bpr files - it will overwrite your wx distribution cpp files!
|
||||||
|
|
||||||
<h4>
|
<h3>
|
||||||
Solution 2</h4>
|
Solution 2</h3>
|
||||||
Creating the files by hand . This is for the calendar sample; you will
|
Creating the files by hand. This is for the calendar sample; you will
|
||||||
have to change the names for the other samples
|
have to change the names for the other samples
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
Create a calendar.mak file [must have the same name as the cpp file] in
|
Create a calendar.mak file [must have the same name as the cpp file] in
|
||||||
a plain text editor with <a href="http://biolpc22.york.ac.uk/wx/bc/calendar.mak">this contents</a></li>
|
a plain text editor with <a href="http://biolpc22.york.ac.uk/wx/bc/calendar.mak">these contents</a></li>:
|
||||||
</ul>
|
</ul>
|
||||||
<tt>#-----------------------------------------------------------------------------</tt>
|
<tt>#-----------------------------------------------------------------------------</tt>
|
||||||
<br><tt>#this is for Borland CBuilder IDE v1 and 3</tt>
|
<br><tt>#this is for Borland CBuilder IDE v1 and 3</tt>
|
||||||
@@ -112,8 +112,9 @@ jpeg.lib for image samples</tt>
|
|||||||
<br>
|
<br>
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
modify the .cpp file to include these<a href="http://biolpc22.york.ac.uk/wx/bc/calendar_include.cpp">
|
modify the .cpp file to include
|
||||||
lines </a>near the top</li>
|
<a href="http://biolpc22.york.ac.uk/wx/bc/calendar_include.cpp">these lines</a>
|
||||||
|
near the top</li>
|
||||||
</ul>
|
</ul>
|
||||||
<tt>#ifdef __BIDE__</tt>
|
<tt>#ifdef __BIDE__</tt>
|
||||||
<br><tt>#define _NO_VCL</tt>
|
<br><tt>#define _NO_VCL</tt>
|
||||||
@@ -126,7 +127,7 @@ if you have more than one .cpp file</tt>
|
|||||||
<br>
|
<br>
|
||||||
<p>In CBuilder 1 you can use <b>Open Project</b> to open the mak file and
|
<p>In CBuilder 1 you can use <b>Open Project</b> to open the mak file and
|
||||||
edit/compile/debug.
|
edit/compile/debug.
|
||||||
<br>In CBuilder 3 and 4, then you can use <b>Open Project </b>and choose
|
<p>In CBuilder 3 and 4, then you can use <b>Open Project</b> and choose
|
||||||
the Open Borland CBuilder 1 Project from the drop down file types. The
|
the Open Borland CBuilder 1 Project from the drop down file types. The
|
||||||
system will modify the mak file and update it for you.
|
system will modify the mak file and update it for you.
|
||||||
<p>Now try compiling it in the ide.
|
<p>Now try compiling it in the ide.
|
||||||
@@ -135,7 +136,7 @@ Hints:</h4>
|
|||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
You can set it up for normal and debug modes (change the -v switch in CFLAG1
|
You can set it up for normal and debug modes (change the -v switch in CFLAG1
|
||||||
and LFLAG)</li>
|
and LFLAG)</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
@@ -144,12 +145,12 @@ a simple editor like notepad to the file minimal.mak (I have had problems
|
|||||||
in CBuilder 1.00 with Unix style line endings)</li>
|
in CBuilder 1.00 with Unix style line endings)</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
If you want to avoid the warnings about hiding virtual methods add <b><tt>-w-hid
|
If you want to avoid the warnings about hiding virtual methods add
|
||||||
</tt></b>to the CFLAGS1 line</li>
|
<b><tt>-w-hid</tt></b> to the CFLAG1 line</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
the #define WinMain WinMain line allows CBuilder to think it has a non-VCL
|
the #define WinMain WinMain line allows CBuilder to think it has a non-VCL
|
||||||
<tt>main </tt>function</li>
|
<tt>main</tt> function</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
the USEUNIT macros tell CBuilder which other source files to include, without
|
the USEUNIT macros tell CBuilder which other source files to include, without
|
||||||
@@ -168,19 +169,19 @@ Solution 3</h3>
|
|||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
download the wxWindows-2.1.15-bcb.zip file,</li>
|
download the wxWindows-2.1.16-bcb.zip file,</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
extract it</li>
|
extract it</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
use the <b><tt>idetomak</tt></b> (CBuilder 1) or <b><tt>idetobpr</tt></b>
|
use the <b><tt>idetomak</tt></b> (CBuilder 1) or <b><tt>idetobpr</tt></b>
|
||||||
(CBuilder 3/4) utility on the <b><tt>.ide</tt></b> file in the samples
|
(CBuilder 3/4) utility on the <b><tt>.ide</tt></b> file in the samples
|
||||||
directory. This modifies the cpp source and makes a "suitable" bpr file
|
directory. This modifies the cpp source and makes a "suitable" mak or bpr file
|
||||||
(at least in CBuilder 1/3/4).</li>
|
(at least in CBuilder 1/3/4).</li>
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
add the location of the wx/include files in the project | options
|
add the location of the wx/include files in the project | options
|
||||||
| directory dialog</li>
|
| directory dialog</li>
|
||||||
</ul>
|
</ul>
|
||||||
I found in CBuilder 1 that the <tt>idetomak</tt> utility did not manage
|
I found in CBuilder 1 that the <tt>idetomak</tt> utility did not manage
|
||||||
@@ -190,13 +191,13 @@ are correct
|
|||||||
<h2>
|
<h2>
|
||||||
Error with ODBC32</h2>
|
Error with ODBC32</h2>
|
||||||
Sometimes you get an error saying that there are unresolved externals in
|
Sometimes you get an error saying that there are unresolved externals in
|
||||||
ODBC. The solution is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
|
ODBC. The solution is to run a command prompt in your <b><tt>wx\lib</tt></b> directory
|
||||||
and use the <b><tt>implib </tt></b>command:
|
and use the <b><tt>implib</tt></b> command:
|
||||||
<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
|
<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
|
||||||
<p>This creates the necessary library, odbc32.lib
|
<p>This creates the necessary library, odbc32.lib
|
||||||
<h2>
|
<h2>
|
||||||
Unresolved Problem</h2>
|
Unresolved Problem</h2>
|
||||||
<tt>In Borland CBuilder 1.00 (with linker service patch) I frequently
|
<tt>In Borland CBuilder 1.00 (with linker service patch) I frequently
|
||||||
get an error</tt>
|
get an error</tt>
|
||||||
<p><tt>Turbo Incremental Link Version 1.0 Copyright (c) 1997 Borland
|
<p><tt>Turbo Incremental Link Version 1.0 Copyright (c) 1997 Borland
|
||||||
International</tt>
|
International</tt>
|
||||||
@@ -209,8 +210,7 @@ line 2060</tt>
|
|||||||
<br><tt>Fatal: Access violation. Program terminated.</tt>
|
<br><tt>Fatal: Access violation. Program terminated.</tt>
|
||||||
<p><tt>** error 2 ** deleting minimal.exe</tt>
|
<p><tt>** error 2 ** deleting minimal.exe</tt>
|
||||||
<p>I have not been able to track down why sometimes this error occurs and
|
<p>I have not been able to track down why sometimes this error occurs and
|
||||||
other times it is OK
|
other times it is OK. I have not seen this in Cbuilder 3 or 4.
|
||||||
<br>I have not seen this in Cbuilder 3 or 4
|
|
||||||
<p>
|
<p>
|
||||||
<hr WIDTH="100%">
|
<hr WIDTH="100%">
|
||||||
<p>Page updated on 31 May 2000 by Chris Elliott
|
<p>Page updated on 31 May 2000 by Chris Elliott
|
||||||
|
Reference in New Issue
Block a user