This commit is contained in:
wiz 2013-05-26 18:22:59 +00:00
parent 66ee92b416
commit 51fbf77318
2 changed files with 41 additions and 20 deletions

View file

@ -7658,7 +7658,7 @@ TOOLS_PLATFORM.true?= true # shell builtin
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div>
<div class="qandaset">
<a name="idm88201136"></a><dl>
<a name="idm76168656"></a><dl>
<dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a>
</dt>
<dt>18.4.2. <a href="#tools.listall">How do I get a list of all available
@ -7677,7 +7677,7 @@ TOOLS_PLATFORM.true?= true # shell builtin
<tbody>
<tr class="question">
<td align="left" valign="top">
<a name="tools.new"></a><a name="idm88200752"></a><p><b>18.4.1.</b></p>
<a name="tools.new"></a><a name="idm76168272"></a><p><b>18.4.1.</b></p>
</td>
<td align="left" valign="top"><p>How do I add a new tool?</p></td>
</tr>
@ -7687,7 +7687,7 @@ TOOLS_PLATFORM.true?= true # shell builtin
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="tools.listall"></a><a name="idm88199728"></a><p><b>18.4.2.</b></p>
<a name="tools.listall"></a><a name="idm76167248"></a><p><b>18.4.2.</b></p>
</td>
<td align="left" valign="top"><p>How do I get a list of all available
tools?</p></td>
@ -7698,7 +7698,7 @@ TOOLS_PLATFORM.true?= true # shell builtin
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="tools.used"></a><a name="idm88198704"></a><p><b>18.4.3.</b></p>
<a name="tools.used"></a><a name="idm76166224"></a><p><b>18.4.3.</b></p>
</td>
<td align="left" valign="top"><p>How can I get a list of all the tools that a
package is using while being built? I want to know whether it
@ -8092,13 +8092,25 @@ ACCEPTABLE_LICENSES+=xv-license
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>If your package needs another package's binaries or
libraries to build or run, and if that package has a
libraries to build and run, and if that package has a
<code class="filename">buildlink3.mk</code> file available, use it:</p>
<pre class="programlisting">
.include "../../graphics/jpeg/buildlink3.mk"
</pre>
</li>
<li class="listitem">
<p>If your package needs another package's binaries or
libraries only for building, and if that package has a
<code class="filename">buildlink3.mk</code> file available, use it:</p>
<pre class="programlisting">
.include "../../graphics/jpeg/buildlink3.mk"
</pre>
<p>but set
<code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>jpeg</code></em>?=build</code>
to make it a build dependency only. This case is rather
rare.</p>
</li>
<li class="listitem">
<p>If your package needs binaries from another package to build,
use the <code class="varname">BUILD_DEPENDS</code> definition:</p>
<pre class="programlisting">
@ -9748,7 +9760,7 @@ place.</p></li>
and if you still don't have the answer, ask on the
<code class="literal">pkgsrc-users</code> mailing list.</p>
<div class="qandaset">
<a name="idm87648304"></a><dl>
<a name="idm77694160"></a><dl>
<dt>22.1. <a href="#devfaq.makeflags">What is the difference between
MAKEFLAGS, .MAKEFLAGS and
MAKE_FLAGS?</a>
@ -9793,7 +9805,7 @@ do?</a>
<tbody>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.makeflags"></a><a name="idm87647920"></a><p><b>22.1.</b></p>
<a name="devfaq.makeflags"></a><a name="idm77693776"></a><p><b>22.1.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
@ -9809,7 +9821,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.make"></a><a name="idm87643824"></a><p><b>22.2.</b></p>
<a name="devfaq.make"></a><a name="idm77689808"></a><p><b>22.2.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
@ -9827,7 +9839,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.cc"></a><a name="idm87639344"></a><p><b>22.3.</b></p>
<a name="devfaq.cc"></a><a name="idm77685328"></a><p><b>22.3.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
@ -9845,7 +9857,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.bl3flags"></a><a name="idm87635248"></a><p><b>22.4.</b></p>
<a name="devfaq.bl3flags"></a><a name="idm77681232"></a><p><b>22.4.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">BUILDLINK_LDFLAGS</code>,
@ -9858,7 +9870,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.bl3prefix"></a><a name="idm87633072"></a><p><b>22.5.</b></p>
<a name="devfaq.bl3prefix"></a><a name="idm77678928"></a><p><b>22.5.</b></p>
</td>
<td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
@ -9874,7 +9886,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.master_sites"></a><a name="idm87629872"></a><p><b>22.6.</b></p>
<a name="devfaq.master_sites"></a><a name="idm77675856"></a><p><b>22.6.</b></p>
</td>
<td align="left" valign="top"><p>What does
<code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
@ -9898,7 +9910,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.mailinglists"></a><a name="idm87613616"></a><p><b>22.7.</b></p>
<a name="devfaq.mailinglists"></a><a name="idm77667792"></a><p><b>22.7.</b></p>
</td>
<td align="left" valign="top"><p>Which mailing lists are there for package
developers?</p></td>
@ -9923,7 +9935,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.documentation"></a><a name="idm87609904"></a><p><b>22.8.</b></p>
<a name="devfaq.documentation"></a><a name="idm77664080"></a><p><b>22.8.</b></p>
</td>
<td align="left" valign="top"><p>Where is the pkgsrc
documentation?</p></td>
@ -9971,7 +9983,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
<a name="devfaq.too-much-time"></a><a name="idm87603376"></a><p><b>22.9.</b></p>
<a name="devfaq.too-much-time"></a><a name="idm77657552"></a><p><b>22.9.</b></p>
</td>
<td align="left" valign="top"><p>I have a little time to kill. What shall I
do?</p></td>

View file

@ -6811,23 +6811,32 @@ The format for a BUILD_DEPENDS and a DEPENDS definition is:
Please note that the "pre-req-package-name" may include any of the wildcard
version numbers recognized by pkg_info(1).
1. If your package needs another package's binaries or libraries to build or
1. If your package needs another package's binaries or libraries to build and
run, and if that package has a buildlink3.mk file available, use it:
.include "../../graphics/jpeg/buildlink3.mk"
2. If your package needs binaries from another package to build, use the
2. If your package needs another package's binaries or libraries only for
building, and if that package has a buildlink3.mk file available, use it:
.include "../../graphics/jpeg/buildlink3.mk"
but set BUILDLINK_DEPMETHOD.jpeg?=build to make it a build dependency only.
This case is rather rare.
3. If your package needs binaries from another package to build, use the
BUILD_DEPENDS definition:
BUILD_DEPENDS+= scons-[0-9]*:../../devel/scons
3. If your package needs a library with which to link and there is no
4. If your package needs a library with which to link and there is no
buildlink3.mk file available, create one. Using DEPENDS won't be sufficient
because the include files and libraries will be hidden from the compiler.
4. If your package needs some executable to be able to run correctly and if
5. If your package needs some executable to be able to run correctly and if
there's no buildlink3.mk file, this is specified using the DEPENDS
variable. The print/lyx package needs to be able to execute the latex
binary from the teTeX package when it runs, and that is specified:
@ -6835,7 +6844,7 @@ version numbers recognized by pkg_info(1).
DEPENDS+= teTeX-[0-9]*:../../print/teTeX
5. You can use wildcards in package dependencies. Note that such wildcard
6. You can use wildcards in package dependencies. Note that such wildcard
dependencies are retained when creating binary packages. The dependency is
checked when installing the binary package and any package which matches
the pattern will be used. Wildcard dependencies should be used with care.