Annotation of htdocs/docs/pkgsrc/configuring.html, revision 1.14

1.1       dsieger     1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
                      2: <html>
                      3: <head>
                      4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
                      5: <title>Chapter 5. Configuring pkgsrc</title>
1.2       rillig      6: <link rel="stylesheet" href="/global.css" type="text/css">
1.1       dsieger     7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
1.11      rillig      8: <link rel="home" href="index.html" title="The pkgsrc guide">
1.1       dsieger     9: <link rel="up" href="users-guide.html" title="Part I. The pkgsrc user's guide">
                     10: <link rel="prev" href="using.html" title="Chapter 4. Using pkgsrc">
                     11: <link rel="next" href="binary.html" title="Chapter 6. Creating binary packages">
                     12: </head>
                     13: <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
                     14: <div class="navheader">
                     15: <table width="100%" summary="Navigation header">
                     16: <tr><th colspan="3" align="center">Chapter 5. Configuring pkgsrc</th></tr>
                     17: <tr>
                     18: <td width="20%" align="left">
                     19: <a accesskey="p" href="using.html">Prev</a> </td>
                     20: <th width="60%" align="center">Part I. The pkgsrc user's guide</th>
                     21: <td width="20%" align="right"> <a accesskey="n" href="binary.html">Next</a>
                     22: </td>
                     23: </tr>
                     24: </table>
                     25: <hr>
                     26: </div>
                     27: <div class="chapter" lang="en">
                     28: <div class="titlepage"><div><div><h2 class="title">
                     29: <a name="configuring"></a>Chapter 5. Configuring pkgsrc</h2></div></div></div>
                     30: <div class="toc">
                     31: <p><b>Table of Contents</b></p>
                     32: <dl>
                     33: <dt><span class="sect1"><a href="configuring.html#general-configuration">5.1. General configuration</a></span></dt>
                     34: <dt><span class="sect1"><a href="configuring.html#variables-affecting-build">5.2. Variables affecting the build process</a></span></dt>
1.6       rillig     35: <dt><span class="sect1"><a href="configuring.html#variables-affecting-installation">5.3. Variables affecting the installation process</a></span></dt>
1.3       rillig     36: <dt><span class="sect1"><a href="configuring.html#conf.compiler">5.4. Selecting and configuring the compiler</a></span></dt>
1.1       dsieger    37: <dd><dl>
1.3       rillig     38: <dt><span class="sect2"><a href="configuring.html#selecting-the-compiler">5.4.1. Selecting the compiler</a></span></dt>
1.11      rillig     39: <dt><span class="sect2"><a href="configuring.html#conf.cflags">5.4.2. Additional flags to the compiler (CFLAGS)</a></span></dt>
                     40: <dt><span class="sect2"><a href="configuring.html#conf.ldflags">5.4.3. Additional flags to the linker (LDFLAGS)</a></span></dt>
1.1       dsieger    41: </dl></dd>
1.3       rillig     42: <dt><span class="sect1"><a href="configuring.html#developer-advanced-settings">5.5. Developer/advanced settings</a></span></dt>
                     43: <dt><span class="sect1"><a href="configuring.html#selecting-build-options">5.6. Selecting Build Options</a></span></dt>
1.1       dsieger    44: </dl>
                     45: </div>
1.3       rillig     46: <a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
1.1       dsieger    47: called <code class="filename">mk.conf</code>. In which directory pkgsrc looks for
                     48: that file depends on the installation. On NetBSD, when you use
1.7       hubertf    49: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it is in the directory
1.1       dsieger    50: <code class="filename">/etc/</code>. In all other cases the default location is
                     51: <code class="literal">${PREFIX}/etc/</code>, depending on where you told the
                     52: bootstrap program to install the binary packages.</p>
                     53: <p>During the bootstrap, an example configuration file is created. To
                     54: use that, you have to create the directory
                     55: <code class="filename">${PREFIX}/etc</code> and copy the example file
                     56: there.</p>
                     57: <p>The format of the configuration file is that of the usual
                     58: BSD-style <code class="filename">Makefile</code>s. The whole pkgsrc configuration
                     59: is done by setting variables in this file. Note that you can define all
                     60: kinds of variables, and no special error checking (for example for
                     61: spelling mistakes) takes place, so you have to try it out to see if it
                     62: works.</p>
                     63: <div class="sect1" lang="en">
                     64: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
                     65: <a name="general-configuration"></a>5.1. General configuration</h2></div></div></div>
                     66: <p>In this section, you can find some variables that apply to all
                     67:     pkgsrc packages. A complete list of the variables that can be
                     68:     configured by the user is available in
                     69:     <code class="filename">mk/defaults/mk.conf</code>, together with some
                     70:     comments that describe each variable's intent.</p>
                     71: <div class="itemizedlist"><ul type="disc">
                     72: <li><p><code class="varname">LOCALBASE</code>: Where
                     73:            packages will be installed. The default is
                     74:            <code class="filename">/usr/pkg</code>. Do not mix binary packages
                     75:            with different <code class="varname">LOCALBASE</code>s!</p></li>
                     76: <li><p><code class="varname">CROSSBASE</code>: Where
                     77:            &#8220;<span class="quote">cross</span>&#8221; category packages will be
                     78:            installed. The default is
                     79:            <code class="filename">${LOCALBASE}/cross</code>.</p></li>
                     80: <li><p><code class="varname">X11BASE</code>: Where
                     81:            X11 is installed on the system. The default is
                     82:            <code class="filename">/usr/X11R6</code>.</p></li>
                     83: <li><p><code class="varname">DISTDIR</code>: Where to store the
                     84:            downloaded copies of the original source distributions used
                     85:            for building pkgsrc packages. The default is
                     86:            <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li>
                     87: <li><p><code class="varname">PKG_DBDIR</code>: Where the
                     88:            database about installed packages is stored.  The default is
                     89:            <code class="filename">/var/db/pkg</code>.</p></li>
                     90: <li><p><code class="varname">MASTER_SITE_OVERRIDE</code>:
                     91:            If set, override the packages'
                     92:            <code class="varname">MASTER_SITES</code> with this value.</p></li>
                     93: <li><p><code class="varname">MASTER_SITE_BACKUP</code>:
                     94:            Backup location(s) for distribution files and patch files
                     95:            if not found locally or in
                     96:            <code class="filename">${MASTER_SITES}</code> or
                     97:            <code class="filename">${PATCH_SITES}</code> respectively.
                     98:            The defaults are
                     99:            <code class="filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}/</code>
                    100:            and
                    101:            <code class="filename">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/</code>.</p></li>
                    102: <li><p><code class="varname">BINPKG_SITES</code>:
                    103:            List of sites carrying binary pkgs. <em class="replaceable"><code>rel</code></em> and
                    104:            <em class="replaceable"><code>arch</code></em> are replaced with OS
                    105:            release (&#8220;<span class="quote">2.0</span>&#8221;, etc.) and architecture
                    106:            (&#8220;<span class="quote">mipsel</span>&#8221;, etc.).</p></li>
                    107: <li><p><code class="varname">ACCEPTABLE_LICENSES</code>:
                    108:            List of acceptable licenses. Whenever you try to build a package
                    109:            whose license is not in this list, you will get an error message
                    110:            that includes instructions on how to change this variable.</p></li>
                    111: </ul></div>
                    112: </div>
                    113: <div class="sect1" lang="en">
                    114: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
                    115: <a name="variables-affecting-build"></a>5.2. Variables affecting the build process</h2></div></div></div>
                    116: <p>XXX
                    117:       </p>
                    118: <div class="itemizedlist"><ul type="disc">
                    119: <li><p><code class="varname">PACKAGES</code>: The top level
                    120:            directory for the binary packages. The default is
                    121:            <code class="filename">${PKGSRCDIR}/packages</code>.</p></li>
                    122: <li><p><code class="varname">WRKOBJDIR</code>:
                    123:            The top level directory where, if defined, the separate
                    124:            working directories will get created, and symbolically
                    125:            linked to from <code class="filename">${WRKDIR}</code> (see below).
                    126:            This is useful for building packages on several
                    127:            architectures, then <code class="filename">${PKGSRCDIR}</code>
                    128:            can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code>
                    129:            is local to every architecture. (It should be noted that
                    130:            <code class="varname">PKGSRCDIR</code> should not be set by the user
1.10      jmcneill  131:            &mdash; it is an internal definition which refers to the
1.1       dsieger   132:            root of the pkgsrc tree. It is possible to have many
                    133:            pkgsrc tree instances.)</p></li>
                    134: <li><p><code class="varname">LOCALPATCHES</code>:
                    135:            Directory for local patches that aren't part of pkgsrc.
1.7       hubertf   136:            See <a class="xref" href="components.html#components.patches" title="11.3. patches/*">Section 11.3, &#8220;patches/*&#8221;</a> for more
1.1       dsieger   137:            information.</p></li>
                    138: <li><p><code class="varname">PKGMAKECONF</code>: Location of
1.7       hubertf   139:            the <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file used by a package's
1.1       dsieger   140:            BSD-style Makefile. If this is not set,
                    141:            <code class="varname">MAKECONF</code> is set to
                    142:            <code class="filename">/dev/null</code> to avoid picking up
                    143:            settings used by builds in <code class="filename">/usr/src</code>.</p></li>
                    144: <li><p><code class="varname">DEPENDS_TARGET</code>:
                    145:            By default, dependencies are only installed, and no binary
                    146:            package is created for them. You can set this variable to
                    147:            <code class="literal">package</code> to automatically create binary
                    148:            packages after installing dependencies.</p></li>
                    149: </ul></div>
                    150: </div>
                    151: <div class="sect1" lang="en">
                    152: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6       rillig    153: <a name="variables-affecting-installation"></a>5.3. Variables affecting the installation process</h2></div></div></div>
1.3       rillig    154: <p>A growing number of packages support installation into a
                    155:     subdirectory of <code class="varname">WRKDIR</code>. This allows a package
                    156:     to be built, before the actual filesystem is touched. DESTDIR
                    157:     support exists in two variations:</p>
                    158: <div class="itemizedlist"><ul type="disc">
                    159: <li><p>Basic DESTDIR support means that the package
                    160:       installation and packaging is still run as
                    161:       root.</p></li>
                    162: <li><p>Full DESTDIR support can run the complete build,
                    163:       installation and packaging as normal user. Root privileges are
                    164:       only needed to add packages.</p></li>
                    165: </ul></div>
                    166: <p>To use the DESTDIR support, set either
                    167:     <code class="varname">USE_DESTDIR=yes</code> to use the basic support for
                    168:     packages that offer it or <code class="varname">USE_DESTDIR=full</code> to
                    169:     get the full support with fallback to basic
                    170:     support. <code class="varname">USE_DESTDIR=full</code> needs <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> version 20070802 (or
                    171:     newer). It might become the default DESTDIR support later.</p>
                    172: <p>DESTDIR support changes the behaviour of various targets
                    173:     slightly. To install a package after building it, use
                    174:     <code class="literal">package-install</code>. <code class="literal">package</code> and
                    175:     <code class="literal">install</code> don't do that any
                    176:     longer. <code class="literal">package-install</code> can be used as
                    177:     <code class="varname">DEPENDS_TARGET</code>.  <code class="literal">bin-install</code>
                    178:     will ask for the root password to install the package and fail,
                    179:     <code class="literal">package-install</code> will ask again.</p>
                    180: <p>With basic DESTDIR support, <strong class="userinput"><code>make
                    181:     clean</code></strong> needs to be run as root.</p>
1.13      imil      182: <p>Considering the <code class="filename">foo/bar</code> package,
                    183:     DESTDIR full support can be tested using the following commands
                    184: 
                    185: </p>
                    186: <pre class="programlisting">
                    187: <code class="prompt">$</code> id
                    188: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
                    189: <code class="prompt">$</code> mkdir $HOME/packages
                    190: <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
                    191: </pre>
                    192: <p>
                    193: 
                    194:     Verify <code class="varname">DESTDIR</code> full support, no root privileges
                    195:     should be needed
                    196: 
                    197: </p>
                    198: <pre class="programlisting">
                    199: <code class="prompt">$</code> make USE_DESTDIR=full install
                    200: </pre>
                    201: <p>
                    202: 
                    203:     Create a package without root privileges
                    204: 
                    205: </p>
                    206: <pre class="programlisting">
                    207: <code class="prompt">$</code> make USE_DESTDIR=full PACKAGES=$HOME/packages package
                    208: </pre>
                    209: <p>
                    210: 
                    211:     For the following command, you must be able to gain root
                    212:     privileges using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
                    213: 
                    214: </p>
                    215: <pre class="programlisting">
                    216: <code class="prompt">$</code> make USE_DESTDIR=full PACKAGES=$HOME/packages package-install
                    217: </pre>
                    218: <p>
                    219: 
                    220:     Then, as a simple user
                    221: 
                    222: </p>
                    223: <pre class="programlisting">
                    224: <code class="prompt">$</code> make clean
                    225: </pre>
                    226: <p>
                    227: 
                    228:     </p>
1.3       rillig    229: </div>
                    230: <div class="sect1" lang="en">
                    231: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
                    232: <a name="conf.compiler"></a>5.4. Selecting and configuring the compiler</h2></div></div></div>
1.1       dsieger   233: <div class="sect2" lang="en">
                    234: <div class="titlepage"><div><div><h3 class="title">
1.3       rillig    235: <a name="selecting-the-compiler"></a>5.4.1. Selecting the compiler</h3></div></div></div>
1.1       dsieger   236: <p>By default, pkgsrc will use GCC to build packages.  This may be
                    237:     overridden by setting the following variables in /etc/mk.conf:</p>
                    238: <div class="variablelist"><dl>
                    239: <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
                    240: <dd>
                    241: <p>This is a list of values specifying the chain of
                    242:          compilers to invoke when building packages.  Valid values
                    243:          are:</p>
                    244: <div class="itemizedlist"><ul type="disc">
                    245: <li><p><code class="varname">distcc</code>:
                    246:            distributed C/C++ (chainable)</p></li>
                    247: <li><p><code class="varname">ccache</code>:
                    248:            compiler cache (chainable)</p></li>
                    249: <li><p><code class="varname">gcc</code>:
                    250:            GNU C/C++ Compiler</p></li>
                    251: <li><p><code class="varname">mipspro</code>:
                    252:            Silicon Graphics, Inc. MIPSpro (n32/n64)</p></li>
                    253: <li><p><code class="varname">mipspro</code>:
                    254:            Silicon Graphics, Inc. MIPSpro (o32)</p></li>
                    255: <li><p><code class="varname">sunpro</code>:
                    256:            Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio</p></li>
                    257: </ul></div>
                    258: <p>The default is
                    259:          &#8220;<span class="quote"><code class="varname">gcc</code></span>&#8221;.  You can use
                    260:          <code class="varname">ccache</code> and/or
                    261:          <code class="varname">distcc</code> with an appropriate
                    262:          <code class="varname">PKGSRC_COMPILER</code> setting,
                    263:          e.g. &#8220;<span class="quote"><code class="varname">ccache gcc</code></span>&#8221;.  This
                    264:          variable should always be terminated with a value for
                    265:          a real compiler.  Note that only one real compiler
                    266:          should be listed (e.g. &#8220;<span class="quote"><code class="varname">sunpro gcc</code></span>&#8221;
                    267:          is not allowed).</p>
                    268: </dd>
                    269: <dt><span class="term"><code class="varname">GCC_REQD</code>:</span></dt>
                    270: <dd><p>This specifies the minimum version of GCC to use
                    271:          when building packages.  If the system GCC doesn't
                    272:          satisfy this requirement, then pkgsrc will build and
                    273:          install one of the GCC packages to use instead.</p></dd>
                    274: </dl></div>
                    275: </div>
                    276: <div class="sect2" lang="en">
                    277: <div class="titlepage"><div><div><h3 class="title">
1.3       rillig    278: <a name="conf.cflags"></a>5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div>
1.1       dsieger   279: <p>If you wish to set the <code class="varname">CFLAGS</code> variable,
                    280:        please make sure to use the <code class="literal">+=</code> operator
                    281:        instead of the <code class="literal">=</code> operator:</p>
                    282: <pre class="programlisting">
                    283: CFLAGS+=        -your -flags
                    284: </pre>
                    285: <p>Using <code class="varname">CFLAGS=</code> (i.e. without the
1.12      jnemeth   286:        &#8220;<span class="quote">+</span>&#8221;) may lead to problems with packages that
                    287:        need to add their own flags.  You may want to take a look
                    288:        at the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html" target="_top"><code class="filename">devel/cpuflags</code></a>
                    289:        package if you're interested in optimization for the current
                    290:        CPU.  Setting <code class="varname">USE_CPUFLAGS</code> to yes in
                    291:        <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> will cause pkgsrc to automatically use cpuflags.</p>
1.1       dsieger   292: </div>
                    293: <div class="sect2" lang="en">
                    294: <div class="titlepage"><div><div><h3 class="title">
1.3       rillig    295: <a name="conf.ldflags"></a>5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div>
1.1       dsieger   296: <p>If you want to pass flags to the linker, both in the configure
                    297: step and the build step, you can do this in two ways.  Either set
                    298: <code class="varname">LDFLAGS</code> or <code class="varname">LIBS</code>.  The difference
                    299: between the two is that <code class="varname">LIBS</code> will be appended to
                    300: the command line, while <code class="varname">LDFLAGS</code> come earlier.
                    301: <code class="varname">LDFLAGS</code> is pre-loaded with rpath settings for ELF
                    302: machines depending on the setting of <code class="varname">USE_IMAKE</code> or
                    303: the inclusion of <code class="filename">mk/x11.buildlink3.mk</code>.  As with
                    304: <code class="varname">CFLAGS</code>, if you do not wish to override these
                    305: settings, use the <code class="literal">+=</code> operator:</p>
                    306: <pre class="programlisting">
                    307: LDFLAGS+=        -your -linkerflags
                    308: </pre>
                    309: </div>
                    310: </div>
                    311: <div class="sect1" lang="en">
                    312: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.3       rillig    313: <a name="developer-advanced-settings"></a>5.5. Developer/advanced settings</h2></div></div></div>
1.1       dsieger   314: <p>XXX
                    315:       </p>
                    316: <div class="itemizedlist"><ul type="disc">
                    317: <li>
                    318: <p><code class="varname">PKG_DEVELOPER</code>:
                    319:            Run some sanity checks that package developers want:
                    320:            </p>
                    321: <div class="itemizedlist"><ul type="circle">
                    322: <li><p>make sure patches apply with zero
                    323:              fuzz</p></li>
                    324: <li><p>run check-shlibs to see that all
                    325:              binaries will find their shared libs.</p></li>
                    326: </ul></div>
                    327: <p>
                    328:        </p>
                    329: </li>
                    330: <li><p><code class="varname">PKG_DEBUG_LEVEL</code>: The level
                    331:        of debugging output which is displayed whilst making and
                    332:        installing the package.  The default value for this is 0,
                    333:        which will not display the commands as they are executed
                    334:        (normal, default, quiet operation); the value 1 will display
                    335:        all shell commands before their invocation, and the value 2
                    336:        will display both the shell commands before their invocation,
1.7       hubertf   337:        and their actual execution progress with <span class="command"><strong>set
1.1       dsieger   338:        -x</strong></span> will be displayed.</p></li>
                    339: </ul></div>
                    340: <p>
                    341:     </p>
                    342: </div>
                    343: <div class="sect1" lang="en">
                    344: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.3       rillig    345: <a name="selecting-build-options"></a>5.6. Selecting Build Options</h2></div></div></div>
1.1       dsieger   346: <p>Some packages have build time options, usually to select
                    347:     between different dependencies, enable optional support for big
                    348:     dependencies or enable experimental features.</p>
                    349: <p>To see which options, if any, a package supports, and which
1.7       hubertf   350:     options are mutually exclusive, run <span class="command"><strong>make
1.1       dsieger   351:     show-options</strong></span>, for example:</p>
                    352: <pre class="programlisting">
                    353:     The following options are supported by this package:
                    354:         ssl      Enable SSL support.
                    355:     Exactly one of the following gecko options is required:
                    356:         firefox  Use firefox as gecko rendering engine.
                    357:         mozilla  Use mozilla as gecko rendering engine.
                    358:     At most one of the following database options may be selected:
                    359:         mysql    Enable support for MySQL database.
                    360:         pgsql    Enable support for PostgreSQL database.
                    361: 
                    362:     These options are enabled by default: firefox
                    363:     These options are currently enabled: mozilla ssl
                    364: </pre>
                    365: <p>The following variables can be defined in
1.7       hubertf   366:     <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> to select which options to
1.1       dsieger   367:     enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>,
                    368:     which can be used to select or disable options for all packages
                    369:     that support them, and
                    370:     <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>,
                    371:     which can be used to select or disable options specifically for
                    372:     package <em class="replaceable"><code>pkgbase</code></em>.  Options listed in
                    373:     these variables are selected, options preceded by &#8220;<span class="quote">-</span>&#8221;
                    374:     are disabled. A few examples:</p>
                    375: <pre class="screen">
1.7       hubertf   376: <code class="prompt">$</code> <span class="command"><strong>grep "PKG.*OPTION" <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a></strong></span>
1.1       dsieger   377: PKG_DEFAULT_OPTIONS=    -arts -dvdread -esound
                    378: PKG_OPTIONS.kdebase=    debug -sasl
                    379: PKG_OPTIONS.apache=     suexec </pre>
1.8       rillig    380: <p>It is important to note that options that were specifically
1.14    ! snj       381:     suggested by the package maintainer must be explicitly removed if
1.8       rillig    382:     you do not wish to include the option.  If you are unsure you can view
                    383:     the current state with <span class="command"><strong>make show-options</strong></span>.</p>
1.1       dsieger   384: <p>The following settings are consulted in the order given, and
                    385:     the last setting that selects or disables an option is
                    386:     used:</p>
                    387: <div class="orderedlist"><ol type="1">
                    388: <li><p>the default options as suggested by the package
                    389:       maintainer</p></li>
                    390: <li><p>the options implied by the settings of legacy
                    391:       variables (see below)</p></li>
                    392: <li><p><code class="varname">PKG_DEFAULT_OPTIONS</code></p></li>
                    393: <li><p><code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code></p></li>
                    394: </ol></div>
                    395: <p>For groups of mutually exclusive options, the last option
                    396:     selected is used, all others are automatically disabled.  If an
                    397:     option of the group is explicitly disabled, the previously
                    398:     selected option, if any, is used.  It is an error if no option
                    399:     from a required group of options is selected, and building the
                    400:     package will fail.</p>
                    401: <p>Before the options framework was introduced, build options
                    402:     were selected by setting a variable (often named
                    403:     <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in
1.7       hubertf   404:     <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> for each option.  To ease
1.1       dsieger   405:     transition to the options framework for the user, these legacy
                    406:     variables are converted to the appropriate options setting
                    407:     (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>)
                    408:     automatically.  A warning is issued to prompt the user to update
1.7       hubertf   409:     <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> to use the options framework
1.1       dsieger   410:     directly.  Support for the legacy variables will be removed
                    411:     eventually.</p>
                    412: </div>
                    413: </div>
                    414: <div class="navfooter">
                    415: <hr>
                    416: <table width="100%" summary="Navigation footer">
                    417: <tr>
                    418: <td width="40%" align="left">
                    419: <a accesskey="p" href="using.html">Prev</a> </td>
                    420: <td width="20%" align="center"><a accesskey="u" href="users-guide.html">Up</a></td>
                    421: <td width="40%" align="right"> <a accesskey="n" href="binary.html">Next</a>
                    422: </td>
                    423: </tr>
                    424: <tr>
                    425: <td width="40%" align="left" valign="top">Chapter 4. Using pkgsrc </td>
                    426: <td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
                    427: <td width="40%" align="right" valign="top"> Chapter 6. Creating binary packages</td>
                    428: </tr>
                    429: </table>
                    430: </div>
                    431: </body>
                    432: </html>

CVSweb <webmaster@jp.NetBSD.org>