| | 1 | = Building !MapServer (GDAL/OGR) with DODS Support = |
| | 2 | |
| | 3 | These instructions are for Linux/UNIX builds. Note tried on windows yet. |
| | 4 | |
| | 5 | Download the following package from the DODS Unidata site which is at http://dods/dods-test/home/download/clientSource.html: |
| | 6 | |
| | 7 | DAP: |
| | 8 | |
| | 9 | ftp://ftp.unidata.ucar.edu/pub/dods/DODS-3.4/source/DODS-dap-3.4.5.tar.gz |
| | 10 | |
| | 11 | 3rd Party Packages (libxml2, libcurl, librx): |
| | 12 | |
| | 13 | ftp://ftp.unidata.ucar.edu/pub/dods/DODS-3.4/source/DODS-packages-3.4.2.tar.gz |
| | 14 | |
| | 15 | Unpack these under a common directory, for instance /u. They will then all unpack into a /u/DODS tree. Build them by cd'ing into /u/DODS and doing a "configure" and "make". This will place the various libraries and include files in /u/DODS/lib and /u/DODS/include. Don't worry about failures building ncview and other applications. We don't need those. |
| | 16 | |
| | 17 | If you are building on a platform that requires the -fPIC flag for code to be included in a shared library (such as Solaris), make sure you provide it when configuring the DODS code. Just the the CFLAGS and CXXFLAGS environment variables to -fPIC before running the DODS configure. |
| | 18 | {{{ |
| | 19 | % setenv CFLAGS -fPIC |
| | 20 | % setenv CXXFLAGS -fPIC |
| | 21 | % configure |
| | 22 | % make |
| | 23 | }}} |
| | 24 | Next download, configure and build GDAL with DODS support. The DODS support is in constant work, so download a nightly snapshot of the GDAL source, not the 1.1.9 release. When you configure it, use the --with-dods-root=/u/DODS (or whatever path you used). |
| | 25 | |
| | 26 | You shouldn't need to do anything special with !MapServer. All the magic is in GDAL/OGR. |
