You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by tn...@apache.org on 2001/11/20 19:57:59 UTC
cvs commit: xml-xerces/c/doc build-other.xml build-winunix.xml createdoc.xml domcount.xml domprint.xml enumval.xml idomcount.xml idomprint.xml memparse.xml pparse.xml redirect.xml samples.xml sax2count.xml sax2print.xml saxcount.xml saxprint.xml stdinparse.xml
tng 01/11/20 10:57:59
Modified: c/doc build-other.xml build-winunix.xml createdoc.xml
domcount.xml domprint.xml enumval.xml idomcount.xml
idomprint.xml memparse.xml pparse.xml redirect.xml
samples.xml sax2count.xml sax2print.xml
saxcount.xml saxprint.xml stdinparse.xml
Log:
Documentation Update: Move samples building instruction to build*.xml for consistency.
Revision Changes Path
1.7 +65 -5 xml-xerces/c/doc/build-other.xml
Index: build-other.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-other.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build-other.xml 2001/10/19 20:17:21 1.6
+++ build-other.xml 2001/11/20 18:57:58 1.7
@@ -100,6 +100,66 @@
(Be sure to maintain the same directory structure that you find under
<code>&XercesCSrcInstallDir;</code>.)</note>
</s3>
+
+ <s3 title="Building Samples">
+ <p>Building the &XercesCName; samples using IBM Visual Age C++ Professional 4.0
+ for OS/2 (VAC++).</p>
+
+ <ul>
+ <li> In the <code>XercesCSrcInstallDir;\samples\Projects\OS2\VACPP40</code> directory,
+ find and edit the VAC++ configuration file <code>basedir.icc</code>.</li>
+
+ <li>All of the directories used to build the samples are defined in
+ <code>basedir.icc</code>. You need to edit the directories to match your system.
+ Here are the directories you need to assign:
+
+ SRC_DIR -- <code>XercesCSrcInstallDir;</code>
+ This is where VAC++ should look to find the samples
+ directories containing the source files.
+ BASE_DIR -- The install directory <code>XercesCSrcInstallDir;</code>.
+ VAC++ will store the compiled samples in the <code>bin</code>
+ directory under BASE_DIR. It will also look for the
+ <code>xerces-c.lib</code> file in the <code>lib</code> directory under BASE_DIR.
+
+ Other directories are set based on these two. You can choose to override them
+ if you wish.</li>
+
+ <li>Save <code>basedir.icc</code></li>
+
+ <li>Start the Command Line in the VAC++ folder.</li>
+
+ <li>Navigate to the <code>XercesCSrcInstallDir;\samples\Projects\OS2\VACPP40</code> directory.</li>
+
+ <li>Run <code>bldsamples.cmd</code></li>
+
+ <li>When <code>build.cmd</code> finishes, review the file <code>compiler.errors</code>.
+ This file should contain only informational messages, almost all complaining about constant
+ values in comparisons.</li>
+
+ <li>You should now have several executable files.</li>
+
+ </ul>
+
+ <p>Rebuilding the Configuration Files</p>
+
+ <p>Although it shouldn't be necessary, if you want to rebuild the VAC++
+ configuration files, you'll need to have Object Rexx running on your system:</p>
+
+ <ul>
+ <li> If you are not currently running Object Rexx, run the SWITCHRX command from
+ a command line, answer "yes" to switching to Object Rexx, and follow the
+ instructions to reboot. (Note: You can switch back to "Classic Rexx" by
+ running SWITCHRX again. But you probably won't need to switch back since
+ Object Rexx runs almost 100% of Classic Rexx programs.)</li>
+
+ <li>In the Projects\OS2\VACPP40 directory, run genICC.cmd. This builds the VAC++
+ configuration files for the samples you have on your system.</li>
+
+
+ <li>Go to the first step above in the "Building asmples for OS/2" section.</li>
+ </ul>
+ </s3>
+
</a>
</faq>
@@ -319,15 +379,15 @@
<li>Built atop CoreServices APIs and a limited number of Carbon APIs;
supports builds for both Mac OS Classic, Carbon, and Mac OS X systems.
</li>
-
+
<li>Has a Mac OS native transcoder that utilizes the built-in Mac OS Unicode
converter [MacOSUnicodeConverter].
</li>
-
+
<li>Has a Mac OS native netaccessor that utilizes the built-in Mac OS URLAccess
routines [MacOSURLAccess].
</li>
-
+
<li>Supports builds from Metroworks CodeWarrior, Apple Project Builder,
and Mac OS X shell.
</li>
@@ -441,7 +501,7 @@
CodeWarrior builds, it is not necessary to shorten file names or set the
type/creator codes as required for CodeWarrior.
</li>
-
+
<li>The Project Builder project builds XercesLib as the framework
Xerces.framework. This framework, however, does not currently include a
correct set of public headers. Any referencing code must have an include
@@ -490,7 +550,7 @@
<p>Apart from the build instructions, above, the most important note
about use of &XercesCName; on the Macintosh is that &XercesCName; expects
all filename paths to be specified in unix syntax. If running natively
- under a Mac OS X system, this path will be the standard posix path as
+ under a Mac OS X system, this path will be the standard posix path as
expected by the shell. The easiest means of creating and interpreting these
paths will be through the routines <code>XMLCreateFullPathFromFSRef</code>
and <code>XMLParsePathToFSRef</code> as declared in the file
1.7 +34 -12 xml-xerces/c/doc/build-winunix.xml
Index: build-winunix.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-winunix.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build-winunix.xml 2001/10/29 17:07:36 1.6
+++ build-winunix.xml 2001/11/20 18:57:58 1.7
@@ -32,10 +32,15 @@
</s3>
<s3 title="Building samples">
- <p>Inside the same workspace (xerces-all.dsw), you'll find several other
+ <p>If you are using the source package, inside the same workspace (xerces-all.dsw), you'll find several other
projects. These are for the samples. Select all the samples and right click
on the selection. Then choose "Build (selection only)" to build all the
samples in one shot.</p>
+
+ <p>If you are using the binary package, load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
+ Microsoft Visual C++ workspace inside your MSVC IDE. Then select all the samples and right click
+ on the selection. Then choose "Build (selection only)" to build all the
+ samples in one shot.</p>
</s3>
</a>
</faq>
@@ -372,21 +377,38 @@
</s3>
<s3 title="Building samples">
- <p>Similarly, you can build the samples by giving the same commands in the
- <code>samples</code> directory.</p>
-
-<source>cd $XERCESCROOT/samples
-runConfigure -plinux -cgcc -xg++
+ <p>The installation process for the samples is same on all UNIX
+ platforms.
+ </p>
+<source>cd &XercesCInstallDir;-linux/samples
+./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
gmake</source>
+ <p>This will create the object files in each sample directory
+ and the executables in ' &XercesCInstallDir;-linux/bin' directory.</p>
- <p>The samples get built in the <code>bin</code> directory. Before you run the
- samples, you must make sure that your library path is set to pick up
- libraries from <code>$XERCESCROOT/lib</code>. If not, type the following to
- set your library path properly.</p>
+ <p>Note that <em>runConfigure</em> is just a helper script and you are free to
+ use <em>./configure</em> with the correct parameters to make it work
+ on any platform-compiler combination of your choice. The script needs the following parameters:
+
+ </p>
+<source>
+Usage: runConfigure "options"
+ where options may be any of the following:
+ -p <platform> (accepts 'aix', 'unixware', 'linux', 'solaris',
+'hp-10', 'hp-11', 'os400', 'irix', 'ptx', 'tru64', 'macosx')
+ -c <C compiler name> (e.g. gcc, xlc or icc)
+ -x <C++ compiler name> (e.g. g++, xlC, or icc)
+ -d (specifies that you want to build debug version)
+ -h (get help on the above commands)
+ -z <extra compiler options>
+</source>
-<source>export LD_LIBRARY_PATH=$XERCESCROOT/lib:$LD_LIBRARY_PATH</source>
- <p>You are now set to run the sample applications.</p>
+ <note><em>NOTE:</em>The code samples in this section assume that you are are working on the Linux binary drop.
+ If you are using some other UNIX flavor, please replace '-linux' with the appropriate
+ platform name in the code samples.</note>
+ <p>To delete all the generated object files and executables, type:</p>
+<source>gmake clean</source>
</s3>
</a>
</faq>
1.4 +0 -18 xml-xerces/c/doc/createdoc.xml
Index: createdoc.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/createdoc.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- createdoc.xml 2000/06/20 02:28:52 1.3
+++ createdoc.xml 2001/11/20 18:57:58 1.4
@@ -8,24 +8,6 @@
memory from scratch. It then reports the elements in the tree that
was just created.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked CreateDOMDocument.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd CreateDOMDocument
-gmake</source>
- <p>This will create the object files in the current directory and the executable named
- CreateDOMDocument in ' &XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running CreateDOMDocument">
<p>The CreateDOMDocument sample illustrates how you can create a DOM tree
1.6 +0 -19 xml-xerces/c/doc/domcount.xml
Index: domcount.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/domcount.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- domcount.xml 2001/10/29 17:07:36 1.5
+++ domcount.xml 2001/11/20 18:57:58 1.6
@@ -8,25 +8,6 @@
constructs the DOM tree and walks through the tree counting
the elements (using just one API call).</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked DOMCount.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd DOMCount
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named DOMCount in ' &XercesCInstallDir;-linux/bin'
- directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running DOMCount">
<p>The DOMCount sample parses an XML file and prints out a count of the number of
1.8 +0 -19 xml-xerces/c/doc/domprint.xml
Index: domprint.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/domprint.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- domprint.xml 2001/10/29 17:07:36 1.7
+++ domprint.xml 2001/11/20 18:57:58 1.8
@@ -8,25 +8,6 @@
through the tree printing each element. It thus dumps the XML back
(output same as SAXPrint).</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked DOMPrint.
- </p>
- </s3>
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd DOMPrint
-gmake</source>
- <p>
- This will create the object files in the current directory and the executable named
- DOMPrint in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running DOMPrint">
<p>The DOMPrint sample parses an XML file, using either a validating
1.5 +0 -18 xml-xerces/c/doc/enumval.xml
Index: enumval.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/enumval.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- enumval.xml 2001/10/29 17:07:36 1.4
+++ enumval.xml 2001/11/20 18:57:58 1.5
@@ -6,24 +6,6 @@
<s2 title="EnumVal">
<p>EnumVal shows how to enumerate the markup decls in a DTD Validator.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked EnumVal.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd EnumVal
-gmake</source>
- <p>This will create the object files in the current directory and the executable named
- EnumVal in ' &XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running EnumVal">
<p>This program parses the specified XML file, then shows how to
enumerate the contents of the validator pools. Essentially,
1.3 +0 -19 xml-xerces/c/doc/idomcount.xml
Index: idomcount.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/idomcount.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- idomcount.xml 2001/10/29 17:07:36 1.2
+++ idomcount.xml 2001/11/20 18:57:58 1.3
@@ -8,25 +8,6 @@
constructs the DOM tree and walks through the tree counting
the elements (using just one API call).</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked IDOMCount.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd IDOMCount
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named IDOMCount in ' &XercesCInstallDir;-linux/bin'
- directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running IDOMCount">
<p>The IDOMCount sample parses an XML file and prints out a count of the number of
1.3 +0 -19 xml-xerces/c/doc/idomprint.xml
Index: idomprint.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/idomprint.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- idomprint.xml 2001/10/29 17:07:36 1.2
+++ idomprint.xml 2001/11/20 18:57:58 1.3
@@ -8,25 +8,6 @@
through the tree printing each element. It thus dumps the XML back
(output same as SAXPrint).</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked IDOMPrint.
- </p>
- </s3>
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd IDOMPrint
-gmake</source>
- <p>
- This will create the object files in the current directory and the executable named
- IDOMPrint in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running IDOMPrint">
<p>The IDOMPrint sample parses an XML file, using either a validating
1.7 +0 -19 xml-xerces/c/doc/memparse.xml
Index: memparse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/memparse.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- memparse.xml 2001/10/29 17:07:36 1.6
+++ memparse.xml 2001/11/20 18:57:58 1.7
@@ -7,25 +7,6 @@
<p>MemParse uses the Validating SAX Parser to parse a memory buffer containing
XML statements, and reports the number of elements and attributes found.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked MemParse.
- </p>
- </s3>
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd MemParse
-gmake</source>
- <p>
- This will create the object files in the current directory and the executable named
- <code>MemParse</code> in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running MemParse">
<p>This program uses the SAX Parser to parse a memory buffer
1.8 +0 -19 xml-xerces/c/doc/pparse.xml
Index: pparse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/pparse.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- pparse.xml 2001/10/29 17:07:36 1.7
+++ pparse.xml 2001/11/20 18:57:58 1.8
@@ -17,25 +17,6 @@
continue on to the end of the file and return false, to let you
know that the parse is done.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked PParse.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd PParse
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named PParse in ' &XercesCInstallDir;-linux/bin'
- directory.</p>
-
- <p>To delete all the generated object files and executables, type:</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running PParse">
<p>PParse parses an XML file and prints out a count of the number of
elements in the file</p>
1.5 +0 -19 xml-xerces/c/doc/redirect.xml
Index: redirect.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/redirect.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- redirect.xml 2001/10/29 17:07:36 1.4
+++ redirect.xml 2001/11/20 18:57:58 1.5
@@ -9,25 +9,6 @@
resolver, traps the call to the external DTD file and redirects
it to another specific file which contains the actual DTD.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked Redirect.
- </p>
- </s3>
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd Redirect
-gmake</source>
- <p>
- This will create the object files in the current directory and the executable named
- Redirect in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running Redirect">
<p>This program illustrates how a XML application can use the SAX EntityResolver
1.10 +8 -90 xml-xerces/c/doc/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- samples.xml 2001/10/29 17:07:36 1.9
+++ samples.xml 2001/11/20 18:57:58 1.10
@@ -3,102 +3,16 @@
<s1 title="&XercesCName; Samples">
- <s2 title="Building the Samples">
<p>&XercesCName; comes packaged with 14 sample applications that
demonstrate salient features of the parser using simple
applications written on top of the SAX and DOM APIs provided by
- the parser.</p>
-
- <p>Once you have set up your PATH variable, you can run the
- samples by opening a command window (or your shell prompt for
- UNIX environments). Sample XML data files are provided in the
- samples/data directory.</p>
-
- <p>The installation process for the samples is same on all UNIX
- platforms.
- Note that <em>runConfigure</em> is just a helper script and you are free to
- use <em>./configure</em> with the correct parameters to make it work
- on any platform-compiler combination of your choice. The script needs the following parameters:
-
- </p>
-<source>
-Usage: runConfigure "options"
- where options may be any of the following:
- -p <platform> (accepts 'aix', 'unixware', 'linux', 'solaris',
-'hp-10', 'hp-11', 'os400', 'irix', 'ptx', 'tru64', 'macosx')
- -c <C compiler name> (e.g. gcc, xlc or icc)
- -x <C++ compiler name> (e.g. g++, xlC, or icc)
- -d (specifies that you want to build debug version)
- -h (get help on the above commands)
- -z <extra compiler options>
-</source>
-
- <note><em>NOTE:</em>The code samples in this section assume that you are are working on the Linux binary drop.
- If you are using some other UNIX flavor, please replace '-linux' with the appropriate
- platform name in the code samples.</note>
+ the parser. Sample XML data files are provided in the samples/data directory.</p>
+ <s2 title="Building the Samples">
+ <p>Please refer to the <jump href="build.html">Build Page</jump> for
+ Build Instructions as per specific platform.</p>
</s2>
- <s2 title="Building the Samples for OS2">
-
- <p>Building the &XercesCName; samples using IBM Visual Age C++ Professional 4.0
- for OS/2 (VAC++).</p>
-
- <ul>
- <li> In the <code>XercesCSrcInstallDir;\samples\Projects\OS2\VACPP40</code> directory,
- find and edit the VAC++ configuration file <code>basedir.icc</code>.</li>
-
- <li>All of the directories used to build the samples are defined in
- <code>basedir.icc</code>. You need to edit the directories to match your system.
- Here are the directories you need to assign:
-
- SRC_DIR -- <code>XercesCSrcInstallDir;</code>
- This is where VAC++ should look to find the samples
- directories containing the source files.
- BASE_DIR -- The install directory <code>XercesCSrcInstallDir;</code>.
- VAC++ will store the compiled samples in the <code>bin</code>
- directory under BASE_DIR. It will also look for the
- <code>xerces-c.lib</code> file in the <code>lib</code> directory under BASE_DIR.
-
- Other directories are set based on these two. You can choose to override them
- if you wish.</li>
-
- <li>Save <code>basedir.icc</code></li>
-
- <li>Start the Command Line in the VAC++ folder.</li>
-
- <li>Navigate to the <code>XercesCSrcInstallDir;\samples\Projects\OS2\VACPP40</code> directory.</li>
-
- <li>Run <code>bldsamples.cmd</code></li>
-
- <li>When <code>build.cmd</code> finishes, review the file <code>compiler.errors</code>.
- This file should contain only informational messages, almost all complaining about constant
- values in comparisons.</li>
-
- <li>You should now have several executable files.</li>
-
- </ul>
-
- <p>Rebuilding the Configuration Files</p>
-
- <p>Although it shouldn't be necessary, if you want to rebuild the VAC++
- configuration files, you'll need to have Object Rexx running on your system:</p>
-
- <ul>
- <li> If you are not currently running Object Rexx, run the SWITCHRX command from
- a command line, answer "yes" to switching to Object Rexx, and follow the
- instructions to reboot. (Note: You can switch back to "Classic Rexx" by
- running SWITCHRX again. But you probably won't need to switch back since
- Object Rexx runs almost 100% of Classic Rexx programs.)</li>
-
- <li>In the Projects\OS2\VACPP40 directory, run genICC.cmd. This builds the VAC++
- configuration files for the samples you have on your system.</li>
-
-
- <li>Go to the first step above in the "Building asmples for OS/2" section.</li>
- </ul>
- </s2>
-
<s2 title="Running the Samples">
<p>The sample applications are dependent on the &XercesCName; shared library
@@ -115,6 +29,10 @@
<p>To set you LIBPATH (on AIX for example), you would type:</p>
<source>export LIBPATH=&XercesCInstallDir;/lib:$LIBPATH</source>
+
+ <p>Once you have set up your PATH variable, you can run the
+ samples by opening a command window (or your shell prompt for
+ UNIX environments).</p>
<s3 title="&XercesCName; Samples">
<ul>
1.3 +0 -19 xml-xerces/c/doc/sax2count.xml
Index: sax2count.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/sax2count.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sax2count.xml 2001/10/29 17:07:36 1.2
+++ sax2count.xml 2001/11/20 18:57:58 1.3
@@ -7,25 +7,6 @@
<p>SAX2Count is the simplest application that counts the elements and characters of
a given XML file using the (event based) SAX2 API.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked SAX2Count.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd SAX2Count
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named
- SAX2Count in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running SAX2Count">
<p>The SAX2Count sample parses an XML file and prints out a count of the number of
1.3 +0 -23 xml-xerces/c/doc/sax2print.xml
Index: sax2print.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/sax2print.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sax2print.xml 2001/10/29 17:07:36 1.2
+++ sax2print.xml 2001/11/20 18:57:58 1.3
@@ -10,29 +10,6 @@
line), but the output has the same information content as the
input.</p>
- <s3 title="Building on Windows">
- <p>Load the
- &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked SAX2Print.
- </p>
- </s3>
-
- <s3 title="Building on UNIX">
-
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd SAX2Print
-gmake</source>
-
- <p>This will create the object files in the current directory
- and the executable named SAX2Print in
- '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running SAX2Print">
<p>The SAX2Print sample parses an XML file and prints out the
1.7 +0 -19 xml-xerces/c/doc/saxcount.xml
Index: saxcount.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/saxcount.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- saxcount.xml 2001/10/29 17:07:36 1.6
+++ saxcount.xml 2001/11/20 18:57:58 1.7
@@ -7,25 +7,6 @@
<p>SAXCount is the simplest application that counts the elements and characters of
a given XML file using the (event based) SAX API.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked SAXCount.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd SAXCount
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named
- SAXCount in '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running SAXCount">
<p>The SAXCount sample parses an XML file and prints out a count of the number of
1.7 +0 -23 xml-xerces/c/doc/saxprint.xml
Index: saxprint.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/saxprint.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- saxprint.xml 2001/10/29 17:07:36 1.6
+++ saxprint.xml 2001/11/20 18:57:58 1.7
@@ -10,29 +10,6 @@
line), but the output has the same information content as the
input.</p>
- <s3 title="Building on Windows">
- <p>Load the
- &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked SAXPrint.
- </p>
- </s3>
-
- <s3 title="Building on UNIX">
-
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd SAXPrint
-gmake</source>
-
- <p>This will create the object files in the current directory
- and the executable named SAXPrint in
- '&XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running SAXPrint">
<p>The SAXPrint sample parses an XML file and prints out the
1.8 +0 -19 xml-xerces/c/doc/stdinparse.xml
Index: stdinparse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/stdinparse.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- stdinparse.xml 2001/10/29 17:07:36 1.7
+++ stdinparse.xml 2001/11/20 18:57:58 1.8
@@ -6,25 +6,6 @@
<s2 title="StdInParse">
<p>StdInParse demonstrates streaming XML data from standard input.</p>
- <s3 title="Building on Windows">
- <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then
- build the project marked StdInParse.</p>
- </s3>
-
- <s3 title="Building on UNIX">
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-cd StdInParse
-gmake</source>
- <p>This will create the object files in the current directory
- and the executable named
- StdInParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>To delete all the generated object files and executables, type:</p>
-<source>gmake clean</source>
- </s3>
-
<s3 title="Running StdInParse">
<p>The StdInParse sample parses an XML file from standard input and prints out a
count of the number of
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org