Run the build.bat Script

In the same cmd.exe window where you ran the setenvironment.bat script enter build -h. The build help text is contained in the following list:

build.bat [-h] [-o=OutFolder] [-c=BuildType] [-a=Action] [-w=WithModule] [-d=BuildDocs]
Help: -h[elp]
OutFolder: -o[utpath]=destination folder for binaries
BuildType: -c[onfig]=release(default), debug
Action: -a[ction]=build(default), buildinstall, install, clean
WithModule: -w[ith]=all(default), fdo, providers, shp, sdf, wfs, wms, arcsde, odbc, mysql, gdal
BuildDocs: -d[ocs]=skip(default), build

NoteIf you give the action option argument a value of buildinstall or install, you must also provide an outpath option argument whose value is not the build folder or one of it subfolders.

The default action is to build all of the FDO core release .dll and .lib files and write them to Fdo subfolders and to build all of the provider release .dll and .lib files and write them to Provider subfolders.

If you only specify the -c=debug option, you get all of the FDO core debug .dll and .lib files written to Fdo subfolders and all of the provider debug .dll and .lib files written to Provider subfolders.

If you specify the -a=buildinstall option, you get the Fdo core and provider .dll files copied to Fdo\Bin in the folder specified using the -o option, .lib files copied to Fdo\Lib in the folder specified using the -o option, and the providers.xml file copied to Fdo\Bin in the folder specified using the -o option.

NoteThe providers.xml file is used by FDO to identify where FDO provider binaries are installed.

If you specify the -w=fdo option, you get FDO .dll and .lib files built and written to Fdo subfolders. If you specified an install option, you get the .dlls copied to Fdo\Bin in the folder specified using the -o option, the .lib files copied to Fdo\Lib in the folder specified using the -o option, and some .h files copied to Fdo\Inc in the folder specified using the -o option.

If you specify the -w=arcsde option, you get the arcsde .dll files built and written to Providers\ArcSDE subfolders. If you specified an install option, you get the .dlls copied to Fdo\Bin in the folder specified using the -o option.

If you specify the -w=gdal option, you get the GRFP* .dll and .lib files built and written to Providers\GDAL subfolders. If you specified an install option, you get the .dll files copied to Fdo\Bin in the folder specified using the -o option and the .lib file copied to Fdo\Lib in the folder specified using the -o option.

If you specify the -w=mysql option, you get the mysql .dll and .lib files and the generic rdbms .dll and .lib files built and written to Providers\GenericRdbms subfolders. If you specified an install option, you get the .dll files copied to Fdo\Bin in the folder specified using the -o option, the .lib files copied to Fdo\Lib in the folder specified using the -o option, some .sql files copied to Fdo\Bin\com in the folder specified using the -o option, and some .h files copied to Fdo\Inc in the folder specified using the -o option.

If you specify the -w=odbc option, you get the odbc .dll and .lib files and the generic rdbms .dll and .lib files built and written to Providers\GenericRdbms subfolders. If you specified an install option, you get the .dll files copied to Fdo\Bin in the folder specified using the -o option, the .lib files copied to Fdo\Lib , in the folder specified using the -o option and some .h files copied to Fdo\Inc in the folder specified using the -o option.

If you specify the -w=sdf option, you get the sdf .dll files built and written to a Providers\SDF subfolder. If you specified an install option, you get the .dll files copied to Fdo\Bin in the folder specified using the -o option and some .h files copied to Fdo\Inc\SDF in the folder specified using the -o option.

If you specify the -w=shp option, you get the shp .dll and .lib files built and written to a Providers\SHP subfolder. If you specified an install option, you get the .dll files copied to Fdo\Bin in the folder specified using the -o option, the .lib file copied to Fdo\Lib in the folder specified using the -o option and some .h files copied to Fdo\Inc\SHP in the folder specified using the -o option.

If you specify the -w=wfs option, you get the wfs .dll files built and written to a Provider\WFS subfolder and you get the ows .dll file built and written to a Utilities\OWS subfolder. If you specified an install option, you get the wfs and ows .dll files copied to Fdo\Bin in the folder specified using the -o option.

If you specify the -w=wms option, you get the wms .dll and .lib files built and written to a Provider\WMS subfolder and an ows .dll file built and written to a Utilities\OWS subfolder. If you specified an install option, you get the wms and ows .dll files copied to Fdo\Bin in the folder specified using the -o optionand some .h files copies to Fdo\Inc in the folder specified using the -o option.

If you specified the -d=build option

and you are building the thirdparty .dll files, you get no effect.
and you are building the FDO core, you get the FDO API unmanaged reference .html files built and written to <buildFolderPath>\Fdo\Docs\HTML\FDO_API and the FDO_API.chm files built and written to <buildFolderPath>\Fdo\Docs. You also get the FDO API managed reference .html files built and written to <buildFolderPath>\Fdo\Docs\HTML\FDO_API_managed and the FDO_API_managed.chm built and written to <buildFolderPath>\Fdo\Docs. If you specified an install option, you get FDO API reference .html copied to <outputFolder\Fdo\Docs\HTML\FDO_API, the FDO API managed reference .html files copied to <outputFolder\Fdo\Docs\HTML\FDO_API_managed, the FDO_API.chm, FDO_API_managed.chm, FDG_FDODevGuide.pdf, and the FET_TheEssentialFDOI.pdf copied to <outputFolder>\Fdo\Docs.
and you are building the ArcSDE provider, you get the ArcSDE API reference .html files built and written to Providers\ArcSDE\Docs\HTML\ArcSDE and the ArcSDE_Provider_API.chm built and written to Providers\ArcSDE\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\ArcSDE and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the GDAL provider, you get no effect.
and you are building the MySQL provider, you get the MySQL API reference .html files built and written to Providers\MySQL\Docs\HTML\MySQL and the MySQL_Provider_API.chm built and written to Providers\MySQL\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\MySQL and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the ODBC provider, you get the ODBC API reference .html files built and written to Providers\ODBC\Docs\HTML\ODBC and the ODBC_Provider_API.chm built and written to Providers\ODBC\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\ODBC and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the SDF provider, you get the SDF API reference .html files built and written to Providers\SDF\Docs\HTML\SDF and the SDF_Provider_API.chm built and written to Providers\SDF\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\SDF and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the SHP provider, you get the SHP API reference .html files built and written to Providers\SHP\Docs\HTML\SHP and the SHP_Provider_API.chm built and written to Providers\SHP\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\SHP and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the WFS provider, you get the WFS API reference .html files built and written to Providers\WFS\Docs\HTML\WFS and the WFS_Provider_API.chm built and written to Providers\WFS\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\WFS and the .chm file copied to <outputFolder>\Fdo\Docs.
and you are building the WMS provider, you get the WMS API reference .html files built and written to Providers\WMS\Docs\HTML\WMS and the WMS_Provider_API.chm built and written to Providers\WMS\Docs. If you specified an install option, you get the .html files copied to <outputFolder>\Fdo\Docs\HTML\WMS and the .chm file copied to <outputFolder>\Fdo\Docs.