Chapter 15. Appendices
Prev |  |

## Chapter 15. Appendices

## 15.1. Values of `USES`

Table 15.1. Values of `USES`

Feature | Arguments | Description
--- | --- | ---
`ada` | (none) | Depends on an Ada-capable compiler, and sets `CC` accordingly.
`bison` | (none), `build`, `run`, `both` | Implies that the port uses `devel/bison` in one way or another. By default, with no arguments or with the `build` argument, it implies `bison` as a build-time dependency, `run` implies a run-time dependency, and `both` implies both run-time and build-time dependencies.
`charsetfix` | (none) | Prevents the port from installing `charset.alias`. This should be installed only by `converters/libiconv`. `CHARSETFIX_MAKEFILEIN` can be set to a path relative to `WRKSRC` if `charset.alias` is not installed by `WRKSRC`/`Makefile.in`.
`cmake` | (none), `outsource` | The port will use CMake for configuring and building. With the `outsource` argument, an out-of-source build will be performed. For more information see Section 6.3.4, “Using `cmake`”.
`desktop-file-utils` | (none) | Implies that the port uses the update-desktop-database from `devel/desktop-file-utils`. This uses will automatically add a post-install step in such a way that the port itself still can specify there own post-install step if needed. It also insert lines into the plist for package install and removal to run update-desktop-database.
`fuse` | (none) | Implies the port will depend on the FUSE library and handle the dependency on the kernel module depending on the version of FreeBSD.
`gettext` | (none), `lib`, `build`, `run` | Implies that the port uses `devel/gettext` in one way or another. By default, with no arguments or with the `lib` argument, implies `gettext` with build-time and run-time dependencies, `build` implies a build-time dependency, and `run` implies a run-time dependency.
`iconv` | (none) | Implies that the port uses `converters/libiconv` as build-time and run-time dependency.
`ncurses` | (none), `base`, `port` | Implies that the port uses ncurses, and causes some useful variables to be set.
`pathfix` | (none) | Look for the `Makefile.in` and `configure` files in the port's associated sources and fix common paths to make sure they respect the FreeBSD hierarchy.
`pkgconfig` | (none), `build`, `run`, `both` | Implies that the port uses `devel/pkgconf` in one way or another. With no arguments or with the `build` argument, it implies `pkg-config` as a build-time dependency; `run` implies a run-time dependency; and `both` implies both run-time and build-time dependencies.
`qmail` | (none), `build`, `run`, `both`, `vars` | Implies that the port uses `mail/qmail` in one way or another. With the `build` argument, it implies `qmail` as a build-time dependency. `run` implies a run-time dependency. Using no argument or the `both` argument implies both run-time and build-time dependencies. `vars` will only set QMAIL variables for the port to use.
`readline` | (none), port | Implies that the port uses readline as library dependency, and sets `CPPFLAGS` and `LDFLAGS` as necessary.
`shared-mime-info` | (none) | Implies that the port uses update-mime-database from `misc/shared-mime-info`. This uses will automatically add a post-install step in such a way that the port itself still can specify there own post-install step if needed. It also insert lines into the plist for package install and removal to run update-mime-data with the correct arguments.
`shebangfix` | (none) | A lot of software uses incorrect locations for script interpreters, most notably `/usr/bin/perl` and `/bin/bash`. This fixes shebang lines in scripts listed in `SHEBANG_FILES`. Currently Perl, Python, Bash, Ruby, and PHP are supported by default. To support another interpreter, set `SHEBANG_LANG` (for example ``SHEBANG_LANG`=lua`), then `lua_OLD_CMD` and `lua_CMD`.
`zenoss` | (none) | Implies the port uses `net-mgmt/zenoss` in one way or another, but largely is used for building zenoss related zenpack ports.

Prev |  |
14.6. The FreeBSD Ports Monitoring System | Home |

This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.