[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[UDUNITS #KER-143836]: Env. Var. for the UDUNITS2 lib path_

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [UDUNITS #KER-143836]: Env. Var. for the UDUNITS2 lib path_
  • Date: Thu, 01 Jun 2017 09:10:31 -0600
Daniel,

> I writing a minor update for the configure script of NCO (see
> https://sourceforge.net/p/nco/bugs/96/). Do there exist default
> environment variable names for variables pointing to the UDUNITS2
> library path and include path?

No. The UDUNITS package doesn't set any environment variables for use outside
the package build process.

> If not, should a user use UDUNITS2_LIB or
> UDUNITS_LIB (and *_INC, respectively)? Or the other way around: should
> the configure script look into UDUNITS2_LIB or UDUNITS_LIB?

I would modify the file "configure.ac" in the NCO package to use the
autoconf(1) macros AC_SEARCH_LIBS and AC_CHECK_HEADER to check for the
installed UDUNITS files. For example:

    AC_CHECK_HEADER([udunits2.h], ,
        [AC_MSG_ERROR([UDUNITS2 header-file not found])])
    AC_SEARCH_LIBS([ut_parse], [udunits2], ,
        [AC_MSG_ERROR([UDUNITS2 library not found])])

This will ensure that the user has set the configure(1) variables CPPFLAGS
and LIBS correctly when configuring the build for the NCO package. For
example:

    ./configure CPPFLAGS='-I /opt/udunits2/include' LIBS='-L /opt/udunits2/lib' 
...

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: KER-143836
Department: Support UDUNITS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.