Next: Include files, Previous: Installation, Up: Using the library [Contents][Index]
Let’s denote as LIBUNISTRING_PREFIX
the value of the ‘--prefix’
option that you passed to configure
while installing this package.
If you didn’t pass any ‘--prefix’ option, then the package is installed
in /usr/local.
Let’s denote as LIBUNISTRING_INCLUDEDIR
the directory where the
include files were installed. This is usually the same as
${LIBUNISTRING_PREFIX}/include
. Except that if you passed an
‘--includedir’ option to configure
, it is the value of that
option.
Let’s further denote as LIBUNISTRING_LIBDIR
the directory where
the library itself was installed. This is the value that you passed
with the ‘--libdir’ option to configure
, or otherwise the
same as ${LIBUNISTRING_PREFIX}/lib
. Recall that when building
in 64-bit mode on a 64-bit GNU/Linux system that supports executables
in either 64-bit mode or 32-bit mode, you should have used the option
--libdir=${LIBUNISTRING_PREFIX}/lib64
.
So that the compiler finds the include files, you have to pass it the
option -I${LIBUNISTRING_INCLUDEDIR}
.
So that the compiler finds the library during its linking pass, you have
to pass it the options -L${LIBUNISTRING_LIBDIR} -lunistring
.
On some systems, in some configurations, you also have to pass options
needed for linking with libiconv
. The autoconf macro
gl_LIBUNISTRING
(see Autoconf macro) deals with this
particularity.