Chapter 6 Special considerations

Table of Contents
6.1 Shared Libraries
6.2 Ports with distribution restrictions
6.3 Using perl
6.4 Using X11
6.5 Using automake, autoconf, and libtool
6.6 Using GNOME
6.7 Using KDE
6.8 Using Bison
6.9 Using Java
6.10 Using Python
6.11 Using Emacs
6.12 Using Ruby
6.13 Using SDL

There are some more things you have to take into account when you create a port. This section explains the most common of those.

6.1 Shared Libraries

If your port installs one or more shared libraries, define a INSTALLS_SHLIB make variable, which will instruct a to run ${LDCONFIG} -m on the directory where the new library is installed (usually PREFIX/lib) during post-install target to register it into the shared library cache. This variable, when defined, will also facilitate addition of an appropriate @exec /sbin/ldconfig -m and @unexec /sbin/ldconfig -R pair into your pkg-plist file, so that a user who installed the package can start using the shared library immediately and de-installation will not cause the system to still believe the library is there.

If you need, you can override the default location where the new library is installed by defining the LDCONFIG_DIRS make variable, which should contain a list of directories into which shared libraries are to be installed. For example if your port installs shared libraries into PREFIX/lib/foo and PREFIX/lib/bar directories you could use the following in your Makefile:

LDCONFIG_DIRS=  %%PREFIX%%/lib/foo %%PREFIX%%/lib/bar

Note that content of LDCONFIG_DIRS is passed through sed(1) just like the rest of pkg-plist, so PLIST_SUB substitutions also apply here. It is recommended that you use %%PREFIX%% for PREFIX, %%LOCALBASE%% for LOCALBASE and %%X11BASE%% for X11BASE.

For questions about the FreeBSD ports system, e-mail <>.
For questions about this documentation, e-mail <>.

Hosting by: Hurra Communications Ltd.
Generated: 2007-01-26 17:58:41