svn commit: r37 - trunk/www/docs/OpenSourceBuild__README.html

gregboone at osgeo.org gregboone at osgeo.org
Fri Jul 21 11:02:29 EDT 2006


Author: gregboone
Date: 2006-07-21 15:02:29+0000
New Revision: 37

Modified:
   trunk/www/docs/OpenSourceBuild__README.html

Log:
FDO2

Modified: trunk/www/docs/OpenSourceBuild__README.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/docs/OpenSourceBuild__README.html?view=diff&rev=37&p1=trunk/www/docs/OpenSourceBuild__README.html&p2=trunk/www/docs/OpenSourceBuild__README.html&r1=36&r2=37
==============================================================================
--- trunk/www/docs/OpenSourceBuild__README.html	(original)
+++ trunk/www/docs/OpenSourceBuild__README.html	2006-07-21 15:02:29+0000
@@ -67,16 +67,16 @@
      
         http://www.activestate.com/ActivePerl
 
-  3. Ensure that the Windows Environment Variables are set as follows:
+  3. Ensure that the FDO Windows Environment Variables are set as follows:
 
-        SET FDO=<FDO OpenSource>\Fdo
-        SET FDOUTILITIES=<FDO OpenSource>\Utilities
-        SET FDOTHIRDPARTY=<FDO OpenSource>\ThirdParty
+        SET FDO=[FDO OpenSource]\Fdo
+        SET FDOUTILITIES=[FDO OpenSource]\Utilities
+        SET FDOTHIRDPARTY=[FDO OpenSource]\ThirdParty
         SET XALANROOT=%FDOTHIRDPARTY%\apache\xml-xalan\c
         SET XERCESCROOT=%FDOTHIRDPARTY%\apache\xml-xerces\c
         SET NLSDIR=%XALANROOT%\Src\xalanc\NLS
 
-  4. In order to build all FDO Windows components, ensure that the Microsoft
+  4. In order to build FDO components, ensure that the Microsoft
      MsBuild tool that is used by the the FDO build process is included in 
      the Windows system PATH.
 
@@ -86,7 +86,7 @@
      ArcSDE 9.1 Client SDK installed and the following environment variable 
      set that points to the installation location:
 
-        set SDEHOME=<ArcSDE developer components path> 
+        set SDEHOME=[ArcSDE developer components path] 
 
      Note that ArcSDE is licensed software and must be obtained from an ESRI vendor.
 
@@ -97,11 +97,11 @@
 
      Following the installation, set the following FDO Windows environment variable:
 
-        set FDOMYSQL=<MySQL developer components path> 
+        set FDOMYSQL=[MySQL developer components path] 
 
      e.g. set FDOMYSQL=c:\Program Files\MySQL\MySQL Server 5.0
 
-  7. OPTIONAL: The FDO build includes several generated .cpp files that were 
+  7. OPTIONAL: The FDO build includes several .cpp files that were 
      generated from source .y files by the Bision and Sed utilities. These 
      files are fairly static therefore they are not automatically regenerated 
      as a part of the standard FDO build process. If changes are made 
@@ -144,7 +144,7 @@
 
         e.g. set PATH=%PATH%;C:\Program Files\GnuWin32\bin
 
-     The optional FDO build script that will need to be executed to rebuild the 
+     The FDO build script that will need to be executed to rebuild the 
      generated cpp source files is:
 
         build_parse.bat
@@ -182,7 +182,7 @@
         set PATH=%PATH%;C:\Program Files\doxygen\bin
         set PATH=%PATH%;C:\Program Files\ATT\Graphviz\bin
 
-  9. NOTE: Use the <FDO OpenSource>\setenvironment.bat script to assist in setting and
+  9. NOTE: Use the [FDO OpenSource]\setenvironment.bat script to assist in setting and
      maintaing the correct environment settings for the FDO build process. 
      This script can be modifed and used to set the correct environment variables 
      and PATH settings.
@@ -299,33 +299,33 @@
 
         FDO:
 
-            cd <FDO OpenSource Location>\Fdo\Unmanaged\bin\win32\Debug
+            cd [FDO OpenSource Location]\Fdo\Unmanaged\bin\win32\Debug
             UnitTest
 
         WMS:
 
-            cd <FDO OpenSource Location>\Providers\WMS\bin\win32\debug
+            cd [FDO OpenSource Location]\Providers\WMS\bin\win32\debug
             UnitTest
 
         SDF:
 
-            cd <FDO OpenSource Location>\Providers\SDF\Src\UnitTest
+            cd [FDO OpenSource Location]\Providers\SDF\Src\UnitTest
             ..\..\bin\win32\Debug\UnitTest
  
         SHP:
 
-            cd <FDO OpenSource Location>\Providers\SHP\Src\UnitTest
+            cd [FDO OpenSource Location]\Providers\SHP\Src\UnitTest
             ..\..\bin\win32\Debug\UnitTest
 
         ArcSDE:
 
-            NOTE: Please refer to <FDO OpenSource Location>\Providers\ArcSDE\UnitTest_README.txt
+            NOTE: Please refer to [FDO OpenSource Location]\Providers\ArcSDE\UnitTest_README.txt
             for details on how to create test users and test data, and which command-line arguments
             to pass to the ArcSDE Provider UnitTest executable in order to point to your
             test server and data.
 
-            cd <FDO OpenSource Location>\Providers\ArcSDE\Src\UnitTest
-            ..\..\bin\win32\Debug\UnitTest <mandatory command-line arguments>
+            cd [FDO OpenSource Location]\Providers\ArcSDE\Src\UnitTest
+            ..\..\bin\win32\Debug\UnitTest [mandatory command-line arguments]
 
 
 -----------------------------
@@ -344,15 +344,15 @@
 
   2. Ensure that the following FDO Environment Variables are set as follows:
 
-       FDO = <FDO OpenSource>/Fdo
-       FDOUTILITIES = <FDO OpenSource>/Providers/Utilities
-       FDOTHIRDPARTY = <FDO OpenSource>/ThirdParty
+       FDO = [FDO OpenSource]/Fdo
+       FDOUTILITIES = [FDO OpenSource]/Providers/Utilities
+       FDOTHIRDPARTY = [FDO OpenSource]/ThirdParty
  
   3. In order to build the ArcSDE Provider, you will need to have the
      ArcSDE 9.1 Client SDK installed and the following environment variable set that 
      points to the installation location:
 
-       SDEHOME=<ArcSDE developer components path> 
+       SDEHOME=[ArcSDE developer components path]
 
      Note that ArcSDE is licensed software and must be obtained from an ESRI vendor.
 
@@ -371,7 +371,7 @@
      recommended. However, if a non-RPM installation of MySQL is chosen, 
      following the installation, set the following FDO environment variable:
   
-       FDOMYSQL=<MySQL developer components path>
+       FDOMYSQL=[MySQL developer components path]
  
   5. In order to build the ODBC Provider, you will need to either 
      
@@ -403,7 +403,7 @@
         the following FDO environment variable to point to the location of the unixODBC 
         components:
 
-           FDOODBC=<unixODBC developer components path>
+           FDOODBC=[unixODBC developer components path]
 
   6. NOTE: To run the unit test, you must set LD_LIBRARY_PATH as follows:
 
@@ -418,7 +418,7 @@
      FDO build process. In order to recompile the .y files into their .cpp and .h
      counterparts, execute the build_parse.sh script.
 
-  9. NOTE: Use the <FDO OpenSource>\setenvironment.sh script to assist in setting and
+  9. NOTE: Use the [FDO OpenSource]\setenvironment.sh script to assist in setting and
      maintaing the correct environment settings for the FDO build process. 
      This script can be modifed and used to set the correct environment variables 
      and PATH settings.
@@ -451,7 +451,7 @@
            tar -xvf fdordbms-3.2.0_G007.tar
 
 
-  2. cd <FDO OpenSource Location>
+  2. cd [FDO OpenSource Location]
 
   3. Use the build_thirdparty.sh script to build the FDO Thirdparty binaries. The following 
      is a general guideline on how to use the build_thirdparty.bat build script.
@@ -516,13 +516,13 @@
             build_linux.sh --a buildonly --w sdf
 
      NOTE: build_linux.sh is a simple helper script that assists developers to build the FDO 
-           components. These scripts supplement stand support of configure and make. We have 
+           components. These scripts supplement standard support of configure and make. We have 
            many components in the FDO architecture and building them all was getting somewhat 
            tedious using straight calls to configure and make. We also found that some 
            developers were not interested in building all components or were only interested 
            in building a subset of the components. 
 
-           The implementation of the above build_linux.sh script in essence calls
+           The implementation of the above build_linux.sh script in essence calls...
  
                aclocal
                libtoolize --force
@@ -532,30 +532,30 @@
                make
                make install
 
-           for the fdocore components as well as the set of FDO providers that are 
+           ...for the fdocore components as well as the set of FDO providers that are 
            currently supported on the OSGeo site. 
 
   5. In order to run the SHP, SDF and ArcSDE Provider Unit Tests:
 
         SDF:
 
-            cd <FDO OpenSource>/Providers/SDF/Src/UnitTest
+            cd [FDO OpenSource]/Providers/SDF/Src/UnitTest
             ./UnitTest
  
         SHP:
 
-            cd <FDO OpenSource>/Providers/SHP/Src/UnitTest
+            cd [FDO OpenSource]/Providers/SHP/Src/UnitTest
             ./UnitTest
  
         ArcSDE:
 
-            Please refer to <FDO OpenSource>\Providers\ArcSDE\UnitTest_README.txt
+            Please refer to [FDO OpenSource]\Providers\ArcSDE\UnitTest_README.txt
             for details on how to create test users and test data, and which 
             command-line arguments to pass to the ArcSDE Provider UnitTest 
             executable in order to point to your test server and data.
 
-            cd <FDO OpenSource>\Providers\ArcSDE\Src\UnitTest
-            ..\..\bin\win32\Debug\UnitTest <mandatory command-line arguments>
+            cd [FDO OpenSource]\Providers\ArcSDE\Src\UnitTest
+            ..\..\bin\win32\Debug\UnitTest [mandatory command-line arguments]
  
 <end>
 </pre>




More information about the Fdo-commits mailing list