| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
1 | <!-- $NetBSD: build.xml,v 1.80 2020/02/24 21:13:56 rillig Exp $ --> | | 1 | <!-- $NetBSD: build.xml,v 1.81 2020/05/03 08:27:10 rillig 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 split into | | 13 | described in the following sections. Each phase is split 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 |
| @@ -441,39 +441,26 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site | | | @@ -441,39 +441,26 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site |
441 | <literal>no</literal> if the platform does not support | | 441 | <literal>no</literal> if the platform does not support |
442 | it.</para></listitem></varlistentry> | | 442 | it.</para></listitem></varlistentry> |
443 | | | 443 | |
444 | <varlistentry><term><varname>WRAPPER_REORDER_CMDS</varname></term> | | 444 | <varlistentry><term><varname>WRAPPER_REORDER_CMDS</varname></term> |
445 | | | 445 | |
446 | <listitem><para>A list of reordering commands. A reordering | | 446 | <listitem><para>A list of reordering commands. A reordering |
447 | command has the form | | 447 | command has the form |
448 | <literal>reorder:l:<replaceable>lib1</replaceable>:<replaceable>lib2</replaceable></literal>. | | 448 | <literal>reorder:l:<replaceable>lib1</replaceable>:<replaceable>lib2</replaceable></literal>. |
449 | It ensures that that | | 449 | It ensures that that |
450 | <literal>-l<replaceable>lib1</replaceable></literal> occurs | | 450 | <literal>-l<replaceable>lib1</replaceable></literal> occurs |
451 | before <literal>-l<replaceable>lib2</replaceable></literal>. | | 451 | before <literal>-l<replaceable>lib2</replaceable></literal>. |
452 | </para></listitem></varlistentry> | | 452 | </para></listitem></varlistentry> |
453 | | | 453 | |
454 | <varlistentry><term><varname>WRAPPER_TRANSFORM_CMDS</varname></term> | | | |
455 | <listitem><para>A list of transformation commands. [TODO: | | | |
456 | investigate further]</para></listitem></varlistentry> | | | |
457 | | | | |
458 | <!-- These should probably be internal variables | | | |
459 | <varlistentry><term><varname>WRAPPEES</varname></term> | | | |
460 | <listitem><para></para></listitem></varlistentry> | | | |
461 | <varlistentry><term><varname>UNWRAP_PATTERNS</varname></term> | | | |
462 | <listitem><para></para></listitem></varlistentry> | | | |
463 | <varlistentry><term><varname>UNWRAP_FILES</varname></term> | | | |
464 | <listitem><para></para></listitem></varlistentry> | | | |
465 | --> | | | |
466 | | | | |
467 | </variablelist> | | 454 | </variablelist> |
468 | </sect1> | | 455 | </sect1> |
469 | | | 456 | |
470 | <sect1 id="build.configure"> | | 457 | <sect1 id="build.configure"> |
471 | <title>The <emphasis>configure</emphasis> phase</title> | | 458 | <title>The <emphasis>configure</emphasis> phase</title> |
472 | | | 459 | |
473 | <para>Most pieces of software need information on the header | | 460 | <para>Most pieces of software need information on the header |
474 | files, system calls, and library routines which are available | | 461 | files, system calls, and library routines which are available |
475 | on the platform they run on. The process of determining this | | 462 | on the platform they run on. The process of determining this |
476 | information is known as configuration, and is usually | | 463 | information is known as configuration, and is usually |
477 | automated. In most cases, a script is supplied with the | | 464 | automated. In most cases, a script is supplied with the |
478 | distfiles, and its invocation results in generation of header | | 465 | distfiles, and its invocation results in generation of header |
479 | files, Makefiles, etc.</para> | | 466 | files, Makefiles, etc.</para> |