Run the build_linux.sh Script
 
 
 

In a terminal window enter cd /home/OpenSource and then enter build --h. The build help text is contained in the following list:

NoteThe --c debug option causes the unit test executables to be built. The --m noconfigure option causes the step of configuring the makefiles to be skipped. The --w fdocore option is the same as --w fdo and --w utilities options combined.

The --w fdo option together with the --a buildinstall option causes libFDO-3.2.0.so and libFDO.la to be written to /usr/local/fdo-3.2.0/lib. Xml schema files are written to /usr/local/fdo-3.2.0/Docs/XmlSchema, Four header files, FdoCommon.h, FdoGeometry.h, Fdo.h, and FdoMessage.h, and three directories, Common, Fdo, and Geometry, are written to /usr/local/fdo-3.2.0/include. FDOMessage.cat to be written to /usr/local/fdo-3.2.0/nls. If you add the --d build option, you will get the API documentation generated and written to /usr/local/fdo-3.2.0/docs/HTML/FDO_API.

The --w utilities option together with the --a buildinstall option causes libFdoOws-3.2.0.so and libFdoOws.la to be written to /usr/local/fdo-3.2.0/lib. There is no documentation generated for utilities.

The --w arcsde option together with the --a buildinstall option causes libArcSDEProvider-3.2.0.so and libArcSDEProvider.la to be written to /usr/local/fdo-3.2.0/lib. The ArcSDE directory is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for ArcSDE.

The --w gdal option together with the --a buildinstall option causes libGRFPOverrides-3.2.0.so, libGRFPOverrides.la, libGRFPProvider-3.2.0.so, and libGRFPProvider.lato be written to /usr/local/fdo-3.2.0/lib. The GdalFile directory is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for GDAL.

The --w sdf option together with the --a buildinstall option causes libSDFProvider-3.2.0.so and libSDFProvider.la to be written to /usr/local/fdo-3.2.0/lib. The SDF directory is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for SDF.

The --w shp option together with the --a buildinstall option causes libSHPOverrides-3.2.0.so, libSHPOverrides.la, libSHPProvider-3.2.0.so, and libSHPProvider.la to be written to /usr/local/fdo-3.2.0/lib. The SHP directory is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for SHP.

The --w wfs option together with the --a buildinstall option causes libWFSProvider-3.2.0.so, and libWFSProvider.la to be written to /usr/local/fdo-3.2.0/lib. There are no header files written to /usr/local/fdo-3.2.0/include. There is no documentation generated for WFS.

The --w wms option together with the --a buildinstall option causes libWMSOverrides-3.2.0.so, libWMSOverrides.la, libWMSProvider-3.2.0.so, and libWMSProvider.la to be written to /usr/local/fdo-3.2.0/lib. The WMS directory is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for WMS.

The --w rdbms option together with the --a buildinstall option causes libFdoMySQL-3.2.0.so, libFdoMySQL.la, libFdoODBC-3.2.0.so, libFdoODBC.la, libSchemaMgr_OV-3.2.0.so, and libSchemaMgr_OV.la to be written to /usr/local/fdo-3.2.0/lib. The directory Rdbms is created in /usr/local/fdo-3.2.0/include. There is no documentation generated for MySQL or ODBC.

Configure and remove the intermediate files produced during the last build using the command ./build_linux.sh –a clean

Configure and uninstall the current distribution, leaving the documentation intact, using the command ./build_linux.sh –a uninstall

Configure, build and install the debug binaries using the command ./build_linux.sh –c debug

Configure and build the release binaries component by component using the following commands.

Build and install the API documentation and install the release binaries using the following commands.

Remove intermediate files from the build directories and uninstall the binaries and include files from the output directories using the following commands.

NoteThe uninstall commands do not delete the API documentation in the docs directory.

Configure, build, and install the debug binaries using the following commands.