xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abag...@locus.apache.org
Subject cvs commit: xml-site/sources/xerces-c faq-parse.xml
Date Wed, 12 Jan 2000 00:51:34 GMT
abagchi     00/01/11 16:51:34

  Modified:    sources/xerces-c faq-parse.xml
  Log:
  Added Build section
  
  Revision  Changes    Path
  1.6       +16 -169   xml-site/sources/xerces-c/faq-parse.xml
  
  Index: faq-parse.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/xerces-c/faq-parse.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq-parse.xml	2000/01/06 01:01:02	1.5
  +++ faq-parse.xml	2000/01/12 00:51:34	1.6
  @@ -180,176 +180,8 @@
       </a>
     </faq>
   
  -  <faq title="How do I use VisualAge for Windows with &XercesCProjectName;?">
   
  -    <q>How do I use VisualAge for Windows with &XercesCProjectName;</q>
   
  -    <a>
  -      <p>IBM VisualAge &XercesCProjectName; for Windows Build Requirements</p>
  -
  -      <ol>
  -        <li>VisualAge C++ Version 4.0 with Fixpak 1: Download the
  -          Fixpak from the IBM VisualAge C++ Professional home page at
  -          <jump href="http://www.software.ibm.com/ad/VisualAge_c++/service/csd.html">
  -http://www.software.ibm.com/ad/VisualAge_c++/service/csd.html
  -          </jump></li>
  -
  -        <li>ICU Build: You should have the ICU Library in the same
  -          directory as the &XercesCProjectName; library. For example if
  -          &XercesCProjectName; is at the top level of the d drive, put the
  -          ICU library also at the top level of d drive
  -          e.g. d:/&XercesCProjectName;, d:/icu.</li>
  -      </ol>
  -
  -      <p>Instructions</p>
  -
  -      <note>These instructions assume that you are installing in
  -        d:\&XercesCSrcInstallDir; Replace d with the appropriate drive
  -        letter.</note>
  -
  -      <ol>
  -        <li>Change directory to d:\&XercesCSrcInstallDir;\Projects\Win32</li>
  -
  -        <li>If a d:\&XercesCSrcInstallDir;\Project\Win32\VACPP40 directory does
  -          not exist, create it.</li>
  -
  -        <li>Copy the IBM VisualAge project file, &XercesCProjectName;X.icc,
  -          to the VACPP40 directory. (If it is not provided in your
  -          download, request it from &lt;&XercesCEmailAddress;&gt;.</li>
  -
  -        <li>From the VisualAge main menu enter the project file name
  -          and path.</li>
  -
  -        <li>When the build finishes the status bar should display the
  -          message: Last Compile completed Successfully with warnings
  -          on date.</li>
  -
  -      </ol>
  -    </a>
  -  </faq>
  -
  -  <faq title="How do I use VisualAge for OS/2 with &XercesCProjectName;?">
  -
  -    <q>How do I use VisualAge for OS/2 with &XercesCProjectName;</q>
  -
  -    <a>
  -      <p>IBM VisualAge &XercesCProjectName;/C++ for Windows Build Requirements</p>
  -
  -      <ol>
  -        <li>VisualAge C++ Version 4.0 with Fixpak 1: Download the
  -          Fixpak from the IBM VisualAge C++ Professional home page at
  -          <jump href="http://www.software.ibm.com/ad/VisualAge_c++/service/csd.html">
  -          http://www.software.ibm.com/ad/VisualAge_c++/service/csd.html
  -          </jump></li>
  -
  -        <li>ICU Build: You should have the ICU Library in the same
  -          directory as the &XercesCProjectName; library. For example if
  -          &XercesCProjectName; is at the top level of the d drive, put the
  -          ICU library also at the top level of d drive
  -          e.g. d:/&XercesCProjectName;, d:/icu.</li>
  -      </ol>
  -
  -      <p>Instructions</p>
  -
  -      <note>These instructions assume that you install in drive
  -        <code>d:\&XercesCSrcInstallDir;</code>. Replace d with the appropriate
drive
  -        letter.
  -      </note>
  -      <ol>
  -        <li>Change directory to
  -        d:\&XercesCSrcInstallDir;\Projects\Win32</li>
  -
  -        <li>If a d:\&XercesCSrcInstallDir;\Project\OS2\VACPP40 directory
  -          does not exist, create it.</li>
  -
  -        <li>Copy the IBM VisualAge project file,
  -          &XercesCProjectName;X.icc, to the VACPP40 directory. (If it is not
  -          provided in your download, request it from
  -          &lt;&XercesCEmailAddress;&gt;.</li>
  -
  -        <li>From the VisualAge main menu enter the project file
  -          name and path.</li>
  -
  -        <li>When the build finishes the status bar displays this message:
  -          Last Compile completed Successfully with warnings on date.</li>
  -      </ol>
  -    </a>
  -  </faq>
  -
  -  <faq title="How do I use CodeWarrior for Macintosh with &XercesCProjectName;">
  -
  -    <q>How do I use CodeWarrior for Macintosh with &XercesCProjectName;</q>
  -    <a>
  -      <p>The directions in this file cover installing and building &XercesCProjectName;
  -        and ICU under the MacOS using CodeWarrior.</p>
  -
  -      <ol>
  -        <li>Create a folder that will contain the &XercesCProjectName; and
  -          ICU distributions. For future reference we will refer to this
  -          folder as "src drop".</li>
  -
  -        <li>Download and uncompress the ICU source distribution and
  -          the &XercesCProjectName; source distribution.  You might also want
  -          to download the binary distributions because they may
  -          contain documentation not present in the source
  -          distribution.  This will create two additional directories;
  -          &XercesCProjectName; and icu Folder. Move these folders into the
  -          "src drop" folder.</li>
  -
  -        <li>Drag the &XercesCProjectName; folder and drop it on to the
  -          "rename file" application located in the same folder as this
  -          readme. This is a MacPerl script that renames files with
  -          names too long to fit in a HFS/HFS+ filesystem.  It also
  -          searches through all of the source code and changes the
  -          #include statements to refer to the new file names.</li>
  -
  -        <li>Move the MacOS folder (in the Projects folder) to "src
  -          drop:&XercesCProjectName;:Projects".</li>
  -
  -        <li>You should be able to open the CodeWarrior project file
  -          "src drop:&XercesCProjectName;:Projects:MacOS:&XercesCProjectName;:&XercesCProjectName;"
  -          and build the &XercesCProjectName; library.</li>
  -
  -        <li>You should also be able to open the CodeWarrior project
  -          file "src drop:&XercesCProjectName;:Projects:MacOS:icu:icu" and
  -          build the ICU library.</li>
  -
  -        <li>If you wish you can create projects for and build the rest
  -          of the tools and test suites.  They are not needed if you
  -          just want to use &XercesCProjectName;.  I suggest that you use the
  -          binary data files distributed with the binary distribution
  -          of ICU instead of creating your own from the text data files
  -          in the ICE source distribution.</li>
  -      </ol>
  -
  -      <p>There are some things to be aware of when creating your own
  -        projects using &XercesCProjectName;.</p>
  -
  -      <ol>
  -        <li>You will need to link against both the ICU and
  -          &XercesCProjectName; libraries.</li>
  -
  -        <li>The options "Always search user paths" and "Interpret DOS
  -          and Unix Paths" are very useful.  Some of the code won't
  -          compile without them set.</li>
  -
  -        <li>Most of the tools and test code will require slight
  -          modification to compile and run correctly (typecasts,
  -          command line parameters, etc), but it is possible to get
  -          them working correctly.</li>
  -
  -        <li>You will most likely have to set up the Access Paths. The
  -          access paths in the &XercesCProjectName; projects should serve as a
  -          good example.</li>
  -      </ol>
  -
  -      <p>If you are having problems getting &XercesCProjectName; working, feel
  -        free to send an email to <jump href="mailto:jbellardo@alumni.calpoly.edu">
  -        jbellardo@alumni.calpoly.edu</jump>. However, help will arrive
  -        only if time permits.</p>
  -    </a>
  -  </faq>
  -
     <faq title="Is &XercesCProjectName; thread-safe?">
   
       <q>Is &XercesCProjectName; thread-safe?</q>
  @@ -385,6 +217,19 @@
       </a>
     </faq>
   
  +	<faq title="Why does my multi-threaded application crash on Solaris?">
  +			 <q>Why does my multi-threaded application crash on Solaris?</q>
  +			 <a>
  +			 <p>The problem appears because the throw call on Solaris 2.6 is not multi-thread
safe.
  +          Sun Microsystems provides a patch to solve this problem. To get the latest patch
for
  +          solving this problem, go to <jump href="http://sunsolve.sun.com">
  +					http://sunsolve.sun.com</jump> and get the appropriate patch for
  +          your operating system. For Intel machines running Solaris, you need to get Patch
ID
  +          104678. For SPARC machines you need to get Patch ID #105591.</p>
  +				</a>
  +	</faq>	
  +	
  +	
     <faq title="How do I find out what version of &XercesCProjectName; I am using?">
   
       <q>How do I find out what version of &XercesCProjectName; I am using?</q>
  @@ -573,7 +418,9 @@
       <a>
         <p>&XercesCProjectName; uses a subset of IBM's International Classes
           for Unicode (ICU) for encoding &amp; Unicode
  -        support. &XercesCFullName; is Unicode 3.0 compliant.</p>
  +        support. &XercesCFullName; is Unicode 3.0 compliant. Please note that
  +				<em>these encodings are supported only if you build &XercesCName; with ICU
library</em>,
  +				not as a standalone library using native encoding support.</p>
   
         <p>Besides ASCII, the following encodings are currrently
         supported:</p>
  
  
  

Mime
View raw message