You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by ar...@locus.apache.org on 2000/06/21 00:51:15 UTC
cvs commit: xml-xerces/c/doc buildc.xml faq-parse.xml
aruna1 00/06/20 15:51:13
Modified: c/doc buildc.xml faq-parse.xml
Log:
Updated typos
Revision Changes Path
1.8 +16 -16 xml-xerces/c/doc/buildc.xml
Index: buildc.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/buildc.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- buildc.xml 2000/06/20 21:17:59 1.7
+++ buildc.xml 2000/06/20 22:51:08 1.8
@@ -19,7 +19,7 @@
<li><link anchor="WCharT">What should I define XMLCh to be?</link></li>
<li><link anchor="BuildUsingLibWWW">How can I generate Xerces-C binaries which includes the
sample NetAccessor implementation using Libwww?</link></li>
- <li><link anchor="BuildSingleThreadedLibrary">How do build a single threaded library on
+ <li><link anchor="BuildSingleThreadedLibrary">How do I build a single threaded library on
Unix platforms?</link></li>
<li><link anchor="LookForHelp">Where can I look for more help?</link></li>
</ul>
@@ -1174,12 +1174,11 @@
</s2>
<anchor name="BuildSingleThreadedLibrary"/>
- <s2 title="How do build a single threaded library on Unix platforms?">
+ <s2 title="How do I build a single-threaded library on Unix platforms?">
- <p>To make a single threaded library on Unix platforms you might have to update
- one or more of <code>Makefile.incl, Makefile.in, runConfigure</code> scripts.
- The following steps for each platform guides you to create a single threaded
- library for Xerces project:</p>
+ <p>To build a single-threaded library on Unix platforms you have to update
+ one or more of the following files <code>Makefile.incl, Makefile.in, runConfigure</code>.
+ The following steps guide you to create a single-threaded library for each platform:</p>
<p>For Aix - </p>
<ul>
@@ -1187,36 +1186,37 @@
<code>xlc</code> and <code>xlC</code> respectively</li>
<li>Replace <code>makeC++SharedLib_r</code> with <code>makeC++SharedLib</code></li>
<li>Remove the flag <code>-D_THREAD_SAFE</code></li>
- <li>Remove inclusion to any threaded libarries from the <code>LIBPATH</code></li>
+ <li>Remove inclusion of any threaded library directories from the <code>LIBPATH</code></li>
<li>Remove inclusion of <code>-lpthreads</code> and <code>-lpthread_compat</code></li>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under AIX specific options
+ <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under AIX specific options
in <code>Makefile.incl</code></li>
</ul>
<p>For Solaris -</p>
<ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under SOLARIS
+ <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under SOLARIS
specific options in <code>Makefile.incl</code></li>
- <li>Remove compiler switches like <code>-mt</code></li>
- <li>Remove <code>-D_REENTRANT</code> flag from compile options</li>
+ <li>Remove compiler switch <code>-mt</code></li>
+ <li>Remove <code>-D_REENTRANT</code> flag from the 'compile' options</li>
<li>Remove inclusion of <code>-lpthread</code></li>
</ul>
<p>For Linux -</p>
<ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under LINUX
+ <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under LINUX
specific options in <code>Makefile.incl</code></li>
- <li>Remove <code>-D_REENTRANT</code> flag from compile options</li>
+ <li>Remove <code>-D_REENTRANT</code> flag from the 'compile' options</li>
<li>Remove inclusion of <code>-lpthread</code></li>
</ul>
<p>For HPUX -</p>
<ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under HP
+ <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under HP
specific options in <code>Makefile.incl</code></li>
- <li>Remove inclusion of <code>-lpthread</code> and <code>-lcma</code></li>
- <li>Remove threading defines like <code>-D_PTHREADS_DRAFT4 -DXML_USE_DCE</code></li>
+ <li>Remove inclusion of <code>-lpthread</code> and <code>-lcma</code></li>
+ <li>Remove threading defines like <code>-D_PTHREADS_DRAFT4 ,
+ -DXML_USE_DCE</code></li>
</ul>
</s2>
1.15 +2 -2 xml-xerces/c/doc/faq-parse.xml
Index: faq-parse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-parse.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- faq-parse.xml 2000/06/20 18:39:56 1.14
+++ faq-parse.xml 2000/06/20 22:51:09 1.15
@@ -432,8 +432,8 @@
aren't really leaks in most application, in that the memory usage does not grow over
time as the XML parser is used and re-used.</p>
- <p>What you are seeing as leaks are infact lazily evaluated data allocated into
- static variables. It gets relesed when the application ends. Now you can make a call
+ <p>What you are seeing as leaks are actually lazily evaluated data allocated into
+ static variables. It gets released when the application ends. Now you can make a call
to <code>XMLPlatformUtil::terminate()</code> to release all the lazily allocated
variables before you exit your program.</p>
</a>