Chapter 15. Using USES Macros

Table of Contents
15.1. An Introduction to USES
15.2. ada
15.3. autoreconf
15.4. blaslapack
15.5. bison
15.6. charsetfix
15.7. cmake
15.8. compiler
15.9. cpe
15.10. cran
15.11. desktop-file-utils
15.12. desthack
15.13. display
15.14. dos2unix
15.15. drupal
15.16. execinfo
15.17. fakeroot
15.18. fam
15.19. fmake
15.20. fonts
15.21. fortran
15.22. fuse
15.23. gecko
15.24. gettext
15.25. gettext-runtime
15.26. gettext-tools
15.27. ghostscript
15.28. gmake
15.29. gperf
15.30. gssapi
15.31. horde
15.32. iconv
15.33. imake
15.34. kmod
15.35. lha
15.36. libarchive
15.37. libedit
15.38. libtool
15.39. localbase
15.40. lua
15.41. makeinfo
15.42. makeself
15.43. metaport
15.44. mono
15.45. motif
15.46. ncurses
15.47. ninja
15.48. node
15.49. objc
15.50. openal
15.51. pathfix
15.52. pear
15.53. perl5
15.54. pgsql
15.55. pkgconfig
15.56. pure
15.57. python
15.58. qmail
15.59. qmake
15.60. readline
15.61. scons
15.62. shared-mime-info
15.63. shebangfix
15.64. tar
15.65. tcl
15.66. terminfo
15.67. tk
15.68. twisted
15.69. uidfix
15.70. uniquefiles
15.71. webplugin
15.72. xfce
15.73. zip
15.74. zope

15.1. An Introduction to USES

USES macros make it easy to declare requirements and settings for a port. They can add dependencies, change building behavior, add metadata to packages, and so on, all by selecting simple, preset values..

Each section in this chapter describes a possible value for USES, along with its possible arguments. Arguments are appeneded to the value after a colon (:). Multiple arguments are separated by commas (,).

Example 15.1. Using Multiple Values
USES=	bison perl

Example 15.2. Adding an Argument
USES=	gmake:lite

Example 15.3. Adding Multiple Arguments
USES=	drupal:7,theme

Example 15.4. Mixing it All Together
USES=	pgsql:9.3+ cpe python:2.7,build

All FreeBSD documents are available for download at http://ftp.FreeBSD.org/pub/FreeBSD/doc/

Questions that are not answered by the documentation may be sent to <freebsd-questions@FreeBSD.org>.
Send questions about this document to <freebsd-doc@FreeBSD.org>.