dbertoni    2002/11/01 10:10:17

  Modified:    c/xdocs/sources/xalan faq.xml readme.xml samples.xml
  Log:
  Fixed glitches and added some information about using GNU make.
  
  Revision  Changes    Path
  1.34      +7 -1      xml-xalan/c/xdocs/sources/xalan/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/faq.xml,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- faq.xml   16 Sep 2002 16:59:29 -0000      1.33
  +++ faq.xml   1 Nov 2002 18:10:17 -0000       1.34
  @@ -62,7 +62,7 @@
   <faq title="Building on UNIX">
   <q>What do I need to rebuild &xslt4c; on UNIX?</q>
   
  -<a><p>To build &xslt4c; on supported UNIX platforms, you need &xml4c; and a 
supported C++ compilers (see the table below).</p>
  +<a><p>To build &xslt4c; on supported UNIX platforms, you need &xml4c;, the GNU make 
utility, and a supported C++ compilers (see the table below).</p>
   <p>For more details see: http://xml.apache.org/xalan-c/readme.html#unix</p>
        <table>
          <tr>
  @@ -88,6 +88,12 @@
       </table>
    <p>For more details see: <link idref="readme" anchor="unix">Steps for doing a UNIX 
build</link>.</p>
   </a></faq>
  +
  +<faq title="Make errors on UNIX platforms">
  +<q>I get errors in the Makefile when running the make utility.  What's wrong?</q>
  +
  +<a><p>You must use the GNU make utility.  Other make utilities may not work with 
the Xalan Makefile</p>
  +</faq>
   
   <faq title="ICU">
   <q>What is ICU and why do I need it?</q>
  
  
  
  1.40      +3 -2      xml-xalan/c/xdocs/sources/xalan/readme.xml
  
  Index: readme.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/readme.xml,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- readme.xml        13 Sep 2002 22:00:45 -0000      1.39
  +++ readme.xml        1 Nov 2002 18:10:17 -0000       1.40
  @@ -148,6 +148,7 @@
     </s3><anchor name="unix"/>
   <s3 title="Steps for doing a UNIX build">
       <ol>
  +      <li>The Xalan build files are written for GNU make, and will not work with 
other make utilities.<br/><br/></li>    
         <li>Set the XERCESCROOT environment variable to the path to the root of 
&xml4c;.<br/><br/></li>    
         <li>Set the XALANCROOT environment variable to the path to the root of the 
&xslt4c;
          distribution.<br/><br/></li>
  @@ -175,8 +176,8 @@
      </s3><anchor name="samples"/>
      <s3 title="Rebuilding a sample application">
      <p>The Windows32 distribution includes a Visual C++ workspace for the sample 
applications. This workspace is in the samples directory. If you modify a sample and 
want to recompile it, you can recompile the .cpp file(s) and rebuild the 
executable.</p>
  -<p>The make files that come with the UNIX distributions include targets for 
rebuilding one or all of the sample applications (with the exception of the ThreadSafe 
sample, which in its current form only runs under Windows). To rebuild one or more 
sample applications, go to the xml-xalan/c/src directory and run<br/><br/>
  -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>make <ref>targ</ref></code><br/><br/>
  +<p>The Makefile that come with the UNIX distributions include targets for 
rebuilding one or all of the sample applications (with the exception of the ThreadSafe 
sample, which in its current form only runs under Windows). To rebuild one or more 
sample applications, go to the xml-xalan/c/src directory and run<br/><br/>
  +&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>gmake <ref>targ</ref></code><br/><br/>
   where <ref>targ</ref> is <code>Samples</code> (all the samples), 
<code>XalanTransform</code>, <code>SimpleTransform</code>,  
<code>StreamTransform</code>, <code>UseStylesheetParam</code>, 
<code>TraceListen</code>, <code>CompileStylesheet</code>, (Windows only) 
<code>ThreadSafe</code>  <code>XPathWrapper</code>, <code>ExternalFunctions</code>,or 
<code>ApacheModuleXSLT</code>.</p>
   <note>For information on building Apache Module, see <link idref="samples" 
anchor="apachemodulexslt">ApacheModuleXSLT</link></note>
      </s3>
  
  
  
  1.36      +4 -4      xml-xalan/c/xdocs/sources/xalan/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/samples.xml,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -r1.35 -r1.36
  --- samples.xml       11 Sep 2002 18:03:53 -0000      1.35
  +++ samples.xml       1 Nov 2002 18:10:17 -0000       1.36
  @@ -284,7 +284,7 @@
     <s2 title="ApacheModuleXSLT">
     <note>This sample must be built with the Apache Web server, and the &xslt4c; 
distribution files do not include a binary
       for ApacheModuleXSLT. Assuming you have installed the Apache server on your 
platform, you can use Visual C++ on Windows to
  -    build ApacheModuleXSLT.dll, or the makefile on UNIX to build xslt_module (with 
the appropriate library suffix).</note>
  +    build ApacheModuleXSLT.dll, or the Makefile on UNIX to build xslt_module (with 
the appropriate library suffix).</note>
       
     <p>What it does: runs as an Apache module on an Apache Web server; performs 
transformations and returns the output to a Web
     browser. You configure Apache to respond to a given URL request for an output 
file (html or txt file in the configuration below)
  @@ -293,11 +293,11 @@
     <p>This sample also illustrates use of the XalanTransformer class and the C API 
defined in src/XalanTransformer/XalanCAPI.h. It returns 
     transformation output in blocks to a callback function, which enables the browser 
to start displaying the result before the transformation
     has been completed.</p>
  -  <note>You may need to adjust the Visual C++ or makefile settings to locate the 
required Apache header files. As shipped, the Visual C++ 
  -  project file looks in \Apache Group\Apache\src\include, and the UNIX makefile 
looks in usr/lib.</note>
  +  <note>You may need to adjust the Visual C++ or Makefile settings to locate the 
required Apache header files. As shipped, the Visual C++ 
  +  project file looks in \Apache Group\Apache\src\include, and the UNIX Makefile 
looks in usr/lib.</note>
     <p>To build the Apache module, follow the instructions in <link idref="readme" 
anchor="win32">Steps for doing a Windows 
     build</link> or <link idref="readme" anchor="unix">Steps for doing a UNIX 
build</link>. For UNIX platforms, you do the build with<br/> 
  -  <code>make ApacheModuleXSLT</code>.</p>
  +  <code>gmake ApacheModuleXSLT</code>.</p>
     <s3 title="Setting up and using ApacheModuleXSLT">
     <p>To use ApacheModuleXSLT, do the following:</p>
     <ol>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to