Changes between Version 1 and Version 2 of autotoolsExamples


Ignore:
Timestamp:
Dec 22, 2015 1:47:09 PM (21 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • autotoolsExamples

    v1 v2  
    11[[PageOutline]]
    2 = Making hdf4 optional for installing rasdaman =
     2= Examples for autotools configuration =
    33
    4 Getting and installing hdf4 libraries can be a daunting
    5 task. Previous versions of rasdaman required by default
    6 that these libraries be found on the system before it
    7 could be configured and hence successfully installed.
     4Below are two examples for introducing components which are compiled only optionally, through explicit specification of the corresponding parameter in the `configure` step (and before compilation through `make`).
    85
    9 It is now possible to install rasdaman with/out hdf4
    10 libraries. A new functionality --with-hdf4 that can be
    11 passed when configuring rasdaman has been added. The
    12 functionality works by checking whether libdf.a and
    13 libmhdf.a are installed. If these libraries are found a
    14 new variable HAVE_HDF with value 1 is passed to the
    15 compiler. This variable is included in conversion/hdf.cc
    16 and conversion/convfactory.cc sources for conditional
    17 compilation. An error message is printed otherwise.
     6
     7== HDF4 as optionally compiled package ==
     8
     9Previous versions of rasdaman required that HDF4 libraries be installed on the system before rasdaman itself could be configured and, hence, successfully installed.
     10However, getting and installing HDF4 libraries can be a daunting task. Making HDF4 support optional, therefore, can ease rasdaman system installation.
     11
     12It is now possible to install rasdaman with/out HDF4 libraries. A `configure` parameter `--with-hdf4` indicates that the corresponding libraries, libdf.a and libmhdf.a, are installed.
     13Technically, if these libraries are found then variable `HAVE_HDF` gets assigned a value of 1. This variable is passed to the compiler where it controls conditional compilation in `conversion/hdf.cc`and `conversion/convfactory.cc`. If `--with-hdf4` is provided, but no HDF4 installed then an error message is generated.
    1814
    1915If the user choses to configure rasdaman without invoking
    20 --with-hdf4 functionality, rasdaman will provide a warning
    21 message that hdf4 presence was not checked but that the user
     16`--with-hdf4` functionality, rasdaman will output a warning
     17message that HDF4 presence was not checked but that the user
    2218would need them in order to use rasdaman. These libraries
    2319are particularly needed for work with rascontrol and hence
    2420interact with the servers/database.
    2521
    26 The following is the piece of code that has been added in
    27 the `configure.ac` script. It should be easy to find it.
     22To achieve this, the following piece of code that has been added in the `configure.ac` script:
    2823{{{
    2924AC_ARG_WITH([hdf4],
     
    4540fi
    4641}}}
    47 Also in the conversion/hdf.cc and conversion/convfactory.cc
    48 the conditional compilation variable HAVE_HDF has been included.
    49 This again is easy to find when one looks at the source codes.
    5042
    51 = Making netcdf optional for installing rasdaman =
     43Further, in the `conversion/hdf.cc` and `conversion/convfactory.cc`
     44the conditional compilation variable `HAVE_HDF` has been included.
     45
     46
     47== !NetCDF as ab optionally compiled package ==
    5248
    5349Similarly, the following code in `configure.ac` adds support for optional compilation of !NetCDF