cvs commit: xml-xerces/c/doc samples.xml

[ar...@locus.apache.org]

aruna1      00/06/23 12:51:53

  Modified:    c/doc    samples.xml
  Log:
  OS/2 related changes
  
  Revision  Changes    Path
  1.5       +60 -0     xml-xerces/c/doc/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- samples.xml	2000/05/24 00:15:03	1.4
  +++ samples.xml	2000/06/23 19:51:52	1.5
  @@ -34,6 +34,66 @@
   
       </s2>
   
  +    <s2 title="Building the Samples for OS2">
  +
  +    <p>Building the Xerces-C 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