Skip to content

Commit

Permalink
adding more dropdown menus
Browse files Browse the repository at this point in the history
  • Loading branch information
lisagoodrich committed Dec 18, 2023
1 parent fbc1478 commit 082420f
Showing 1 changed file with 36 additions and 36 deletions.
72 changes: 36 additions & 36 deletions docs/Users_Guide/installation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -231,53 +231,53 @@ Environment Variable Descriptions
External Library Handling in compile_MET_all.sh
-----------------------------------------------

**IF THE USER WANTS TO HAVE THE COMPILATION SCRIPT DOWNLOAD THE LIBRARY DEPENDENCIES**
.. dropdown:: IF THE USER WANTS TO HAVE THE COMPILATION SCRIPT DOWNLOAD THE LIBRARY DEPENDENCIES

The **compile_MET_all.sh** script will compile and install MET and its required external
library dependencies
:ref:`required_external_libraries_to_build_MET`, if needed.
Note that if these libraries are already installed somewhere on the system,
MET will call and use the libraries that were installed by the script.
The **compile_MET_all.sh** script will compile and install MET and its required external
library dependencies
:ref:`required_external_libraries_to_build_MET`, if needed.
Note that if these libraries are already installed somewhere on the system,
MET will call and use the libraries that were installed by the script.


**IF THE USER ALREADY HAS THE LIBRARY DEPENDENCIES INSTALLED**
.. dropdown::IF THE USER ALREADY HAS THE LIBRARY DEPENDENCIES INSTALLED
If the required external library dependencies have already been installed and don’t
need to be reinstalled, or if compiling MET on a machine that uses modulefiles and
the user would like to make use of the existing dependent libraries on that machine,
there are more environment variables that need to be set to let MET know where those
library and header files are. The following environment variables need to be added
to the environment configuration file:
If the required external library dependencies have already been installed and don’t
need to be reinstalled, or if compiling MET on a machine that uses modulefiles and
the user would like to make use of the existing dependent libraries on that machine,
there are more environment variables that need to be set to let MET know where those
library and header files are. The following environment variables need to be added
to the environment configuration file:
**Always Required:**
**MET_BUFRLIB**, **BUFRLIB_NAME**, **MET_PROJ**, **MET_HDF5**, **MET_NETCDF**,
**MET_GSL.**
**Always Required:**
**MET_BUFRLIB**, **BUFRLIB_NAME**, **MET_PROJ**, **MET_HDF5**, **MET_NETCDF**,
**MET_GSL.**
**Optional, Depending on Configuration Options: MET_GRIB2CLIB, MET_GRIB2CINC,
GRIB2CLIB_NAME, LIB_JASPER, LIB_PNG, LIB_Z, MET_ATLAS, MET_ECKIT,
MET_HDF, MET_HDFEOS, MET_CAIRO, MET_FREETYPE, MET_PYTHON_BIN_EXE, MET_PYTHON_CC,
MET_PYTHON_LD.**
**Optional, Depending on Configuration Options: MET_GRIB2CLIB, MET_GRIB2CINC,
GRIB2CLIB_NAME, LIB_JASPER, LIB_PNG, LIB_Z, MET_ATLAS, MET_ECKIT,
MET_HDF, MET_HDFEOS, MET_CAIRO, MET_FREETYPE, MET_PYTHON_BIN_EXE, MET_PYTHON_CC,
MET_PYTHON_LD.**
Generally speaking, for each library there is a set of three environment variables to
describe the locations:
**$MET_<lib>**, **$MET_<lib>INC** and **$MET_<lib>LIB**.
Generally speaking, for each library there is a set of three environment variables to
describe the locations:
**$MET_<lib>**, **$MET_<lib>INC** and **$MET_<lib>LIB**.
The $MET_<lib> environment variable can be used if the external library is
installed such that there is a main directory which has a subdirectory called
*lib* containing the library files and another subdirectory called
*include* containing the include files.
The $MET_<lib> environment variable can be used if the external library is
installed such that there is a main directory which has a subdirectory called
*lib* containing the library files and another subdirectory called *include*
containing the include files.
Alternatively, the $MET_<lib>INC and $MET_<lib>LIB environment variables are used if the
library and include files for an external library are installed in separate locations.
In this case, both environment variables must be specified and the associated
$MET_<lib> variable will be ignored.
Alternatively, the $MET_<lib>INC and $MET_<lib>LIB environment variables are used if the
library and include files for an external library are installed in separate locations.
In this case, both environment variables must be specified and the associated
$MET_<lib> variable will be ignored.
**FINAL NOTE ON EXTERNAL LIBRARIES**
.. dropdown:: FINAL NOTE ON EXTERNAL LIBRARIES

For users wishing to run the Plot-MODE-Field tool, the Ghostscript
`font data <http://sourceforge.net/projects/gs-fonts>`_ must be
downloaded and the **MET_FONT_DIR** environment variable in the
**install_met_env.<machine_name>** file should point to the directory containing those fonts.
For users wishing to run the Plot-MODE-Field tool, the Ghostscript
`font data <http://sourceforge.net/projects/gs-fonts>`_ must be
downloaded and the **MET_FONT_DIR** environment variable in the
**install_met_env.<machine_name>** file should point to the directory containing those fonts.

Executing the compile_MET_all.sh script
---------------------------------------
Expand Down

0 comments on commit 082420f

Please sign in to comment.