| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
| 1 | <!-- $NetBSD: build.xml,v 1.55 2008/07/27 19:27:37 joerg Exp $ --> | | 1 | <!-- $NetBSD: build.xml,v 1.56 2008/09/09 00:59:51 obache Exp $ --> |
| 2 | | | 2 | |
| 3 | <chapter id="build"> | | 3 | <chapter id="build"> |
| 4 | <title>The build process</title> | | 4 | <title>The build process</title> |
| 5 | | | 5 | |
| 6 | <sect1 id="build.intro"> | | 6 | <sect1 id="build.intro"> |
| 7 | <title>Introduction</title> | | 7 | <title>Introduction</title> |
| 8 | | | 8 | |
| 9 | <para>This chapter gives a detailed description on how a package is | | 9 | <para>This chapter gives a detailed description on how a package is |
| 10 | built. Building a package is separated into different | | 10 | built. Building a package is separated into different |
| 11 | <emphasis>phases</emphasis> (for example <varname>fetch</varname>, | | 11 | <emphasis>phases</emphasis> (for example <varname>fetch</varname>, |
| 12 | <varname>build</varname>, <varname>install</varname>), all of which are | | 12 | <varname>build</varname>, <varname>install</varname>), all of which are |
| 13 | described in the following sections. Each phase is splitted into | | 13 | described in the following sections. Each phase is splitted into |
| 14 | so-called <emphasis>stages</emphasis>, which take the name of the | | 14 | so-called <emphasis>stages</emphasis>, which take the name of the |
| @@ -203,27 +203,27 @@ GTKDIR_DEFAULT= ${LOCALBASE} | | | @@ -203,27 +203,27 @@ GTKDIR_DEFAULT= ${LOCALBASE} |
| 203 | the <emphasis>wrappers</emphasis>.</para></listitem></varlistentry> | | 203 | the <emphasis>wrappers</emphasis>.</para></listitem></varlistentry> |
| 204 | | | 204 | |
| 205 | <varlistentry><term><varname>WRKSRC</varname></term> | | 205 | <varlistentry><term><varname>WRKSRC</varname></term> |
| 206 | <listitem><para>This is an absolute pathname pointing to the directory | | 206 | <listitem><para>This is an absolute pathname pointing to the directory |
| 207 | where the distfiles are extracted. It is usually a direct subdirectory | | 207 | where the distfiles are extracted. It is usually a direct subdirectory |
| 208 | of <varname>WRKDIR</varname>, and often it's the only directory entry | | 208 | of <varname>WRKDIR</varname>, and often it's the only directory entry |
| 209 | that isn't hidden. This variable may be changed by a package | | 209 | that isn't hidden. This variable may be changed by a package |
| 210 | <filename>Makefile</filename>.</para></listitem></varlistentry> | | 210 | <filename>Makefile</filename>.</para></listitem></varlistentry> |
| 211 | | | 211 | |
| 212 | </variablelist> | | 212 | </variablelist> |
| 213 | | | 213 | |
| 214 | <para>The <varname>CREATE_WRKDIR_SYMLINK</varname> definition takes either | | 214 | <para>The <varname>CREATE_WRKDIR_SYMLINK</varname> definition takes either |
| 215 | the value <emphasis>yes</emphasis> or <emphasis>no</emphasis> and defaults | | 215 | the value <emphasis>yes</emphasis> or <emphasis>no</emphasis> and defaults |
| 216 | to <emphasis>yes</emphasis>. It indicates whether a symbolic link to the | | 216 | to <emphasis>no</emphasis>. It indicates whether a symbolic link to the |
| 217 | <varname>WRKDIR</varname> is to be created in the pkgsrc entry's directory. | | 217 | <varname>WRKDIR</varname> is to be created in the pkgsrc entry's directory. |
| 218 | If users would like to have their pkgsrc trees behave in a | | 218 | If users would like to have their pkgsrc trees behave in a |
| 219 | read-only manner, then the value of | | 219 | read-only manner, then the value of |
| 220 | <varname>CREATE_WRKDIR_SYMLINK</varname> should be set to | | 220 | <varname>CREATE_WRKDIR_SYMLINK</varname> should be set to |
| 221 | <emphasis>no</emphasis>.</para> | | 221 | <emphasis>no</emphasis>.</para> |
| 222 | </sect1> | | 222 | </sect1> |
| 223 | | | 223 | |
| 224 | <sect1 id="build.running"> | | 224 | <sect1 id="build.running"> |
| 225 | <title>Running a phase</title> | | 225 | <title>Running a phase</title> |
| 226 | | | 226 | |
| 227 | <para>You can run a particular phase by typing <command>make | | 227 | <para>You can run a particular phase by typing <command>make |
| 228 | phase</command>, where <emphasis>phase</emphasis> is the name of the | | 228 | phase</command>, where <emphasis>phase</emphasis> is the name of the |
| 229 | phase. This will automatically run all phases that are required for this | | 229 | phase. This will automatically run all phases that are required for this |