Annotation of htdocs/docs/pkgsrc/creating.html, revision 1.131
1.120 sevan 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
1.1 dsieger 2: <html>
3: <head>
4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.128 rillig 5: <title>Chapter 12. Creating a new pkgsrc package from scratch</title>
1.26 spz 6: <link rel="stylesheet" type="text/css" href="/global.css">
1.1 dsieger 7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
1.15 rillig 8: <link rel="home" href="index.html" title="The pkgsrc guide">
1.1 dsieger 9: <link rel="up" href="developers-guide.html" title="Part II. The pkgsrc developer's guide">
1.128 rillig 10: <link rel="prev" href="help-devel.html" title="Chapter 11. Getting help">
11: <link rel="next" href="components.html" title="Chapter 13. Package components - files, directories and contents">
1.1 dsieger 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">
1.128 rillig 16: <tr><th colspan="3" align="center">Chapter 12. Creating a new pkgsrc package from scratch</th></tr>
1.1 dsieger 17: <tr>
18: <td width="20%" align="left">
1.128 rillig 19: <a accesskey="p" href="help-devel.html">Prev</a> </td>
1.1 dsieger 20: <th width="60%" align="center">Part II. The pkgsrc developer's guide</th>
21: <td width="20%" align="right"> <a accesskey="n" href="components.html">Next</a>
22: </td>
23: </tr>
24: </table>
25: <hr>
26: </div>
1.42 asau 27: <div class="chapter">
1.1 dsieger 28: <div class="titlepage"><div><div><h2 class="title">
1.128 rillig 29: <a name="creating"></a>Chapter 12. Creating a new pkgsrc package from scratch</h2></div></div></div>
1.1 dsieger 30: <div class="toc">
31: <p><b>Table of Contents</b></p>
1.100 leot 32: <dl class="toc">
1.128 rillig 33: <dt><span class="sect1"><a href="creating.html#creating.common">12.1. Common types of packages</a></span></dt>
1.1 dsieger 34: <dd><dl>
1.128 rillig 35: <dt><span class="sect2"><a href="creating.html#creating.perl-module">12.1.1. Perl modules</a></span></dt>
36: <dt><span class="sect2"><a href="creating.html#creating.python-module">12.1.2. Python modules and programs</a></span></dt>
1.1 dsieger 37: </dl></dd>
1.128 rillig 38: <dt><span class="sect1"><a href="creating.html#creating.examples">12.2. Examples</a></span></dt>
39: <dd><dl><dt><span class="sect2"><a href="creating.html#creating.nvu">12.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
1.1 dsieger 40: </dl>
41: </div>
42: <p>When you find a package that is not yet in pkgsrc, you
43: most likely have a URL from where you can download the source
44: code. Starting with this URL, creating a package involves only a
45: few steps.</p>
1.24 wiz 46: <div class="procedure"><ol class="procedure" type="1">
1.126 leot 47: <li class="step"><p>First, install the packages <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a> and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>.</p></li>
1.42 asau 48: <li class="step"><p>Then, choose one of the top-level directories as the
1.1 dsieger 49: category in which you want to place your package. You can also create a
50: directory of your own (maybe called <code class="filename">local</code>). In that
51: category directory, create another directory for your package and change
52: into it.</p></li>
1.42 asau 53: <li class="step"><p>Run the program <span class="command"><strong>url2pkg</strong></span>, which will ask
1.1 dsieger 54: you for a URL. Enter the URL of the distribution file (in most cases a
55: <code class="filename">.tar.gz</code> file) and watch how the basic ingredients
56: of your package are created automatically. The distribution file is
57: extracted automatically to fill in some details in the
58: <code class="filename">Makefile</code> that would otherwise have to be done
59: manually.</p></li>
1.42 asau 60: <li class="step">
1.1 dsieger 61: <p>Examine the extracted files to determine the dependencies of
62: your package. Ideally, this is mentioned in some
63: <code class="filename">README</code> file, but things may differ. For each of
64: these dependencies, look where it exists in pkgsrc, and if there is a
65: file called <code class="filename">buildlink3.mk</code> in that directory, add a
66: line to your package <code class="filename">Makefile</code> which includes that
67: file just before the last line. If the
1.26 spz 68: <code class="filename">buildlink3.mk</code> file does not exist, it must be
69: created first. The <code class="filename">buildlink3.mk</code> file makes sure that the package's include files and libraries are provided.</p>
70: <p>If you just need binaries from a package, add a
1.1 dsieger 71: <code class="varname">DEPENDS</code> line to the Makefile, which specifies the
72: version of the dependency and where it can be found in pkgsrc. This line
73: should be placed in the third paragraph. If the dependency is only
74: needed for building the package, but not when using it, use
1.129 leot 75: <code class="varname">TOOL_DEPENDS</code> or <code class="varname">BUILD_DEPENDS</code>
76: instead of <code class="varname">DEPENDS</code>.
77: The difference between <code class="varname">TOOL_DEPENDS</code> and
78: <code class="varname">BUILD_DEPENDS</code> occurs when cross-compiling:
79: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
80: packages, i.e. packages for the architecture where the package
81: is built;
82: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
83: packages, i.e. packages for the architecture for which the package
84: is built.
1.1 dsieger 85: Your package may then look like this:</p>
86: <pre class="programlisting">
87: [...]
88:
1.129 leot 89: TOOL_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
1.1 dsieger 90: DEPENDS+= screen-[0-9]*:../../misc/screen
91: DEPENDS+= screen>=4.0:../../misc/screen
92:
93: [...]
94:
95: .include "../../<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>package</code></em>/buildlink3.mk"
96: .include "../../devel/glib2/buildlink3.mk"
97: .include "../../mk/bsd.pkg.mk"
98: </pre>
99: </li>
1.42 asau 100: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need
1.24 wiz 101: to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't
1.10 hubertf 102: know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint
103: --explain</strong></span> or <span class="command"><strong>pkglint
1.1 dsieger 104: -e</strong></span>, which outputs additional
105: explanations.</p></li>
1.42 asau 106: <li class="step"><p>In many cases the package is not yet ready to build. You can
1.128 rillig 107: find instructions for the most common cases in the next section, <a class="xref" href="creating.html#creating.common" title="12.1. Common types of packages">Section 12.1, “Common types of packages”</a>. After you have followed the instructions
1.1 dsieger 108: over there, you can hopefully continue here.</p></li>
1.42 asau 109: <li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working
1.1 dsieger 110: directory from the extracted files. Besides these files, a lot of cache
111: files and other system information has been saved in the working
112: directory, which may become wrong after you edited the
113: <code class="filename">Makefile</code>.</p></li>
1.42 asau 114: <li class="step"><p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For
1.128 rillig 115: the various things that can go wrong in this phase, consult <a class="xref" href="fixes.html" title="Chapter 21. Making your package work">Chapter 21, <i>Making your package work</i></a>.</p></li>
1.42 asau 116: <li class="step"><p>When the package builds fine, the next step is to install
1.10 hubertf 117: the package. Run <span class="command"><strong>bmake install</strong></span> and hope that
1.1 dsieger 118: everything works.</p></li>
1.42 asau 119: <li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which
1.1 dsieger 120: contains a list of the files that are installed by the package, is
1.10 hubertf 121: nearly empty. Run <span class="command"><strong>bmake print-PLIST
1.1 dsieger 122: >PLIST</strong></span> to generate a probably correct list. Check
123: the file using your preferred text editor to see if the list of
124: files looks plausible.</p></li>
1.42 asau 125: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated
1.1 dsieger 126: <code class="filename">PLIST</code> contains garbage or not.</p></li>
1.42 asau 127: <li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package
1.1 dsieger 128: has been registered in the database of installed files, but with an
1.10 hubertf 129: empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span>
130: and <span class="command"><strong>bmake install</strong></span> again. Now the package is
1.1 dsieger 131: registered with the list of files from
132: <code class="filename">PLIST</code>.</p></li>
1.42 asau 133: <li class="step"><p>Run <span class="command"><strong>bmake package</strong></span> to create a binary
1.1 dsieger 134: package from the set of installed files.</p></li>
135: </ol></div>
1.42 asau 136: <div class="sect1">
1.1 dsieger 137: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.128 rillig 138: <a name="creating.common"></a>12.1. Common types of packages</h2></div></div></div>
1.42 asau 139: <div class="sect2">
1.1 dsieger 140: <div class="titlepage"><div><div><h3 class="title">
1.128 rillig 141: <a name="creating.perl-module"></a>12.1.1. Perl modules</h3></div></div></div>
1.1 dsieger 142: <p>Simple Perl modules are handled automatically by
1.10 hubertf 143: <span class="command"><strong>url2pkg</strong></span>, including dependencies.</p>
1.1 dsieger 144: </div>
1.42 asau 145: <div class="sect2">
1.1 dsieger 146: <div class="titlepage"><div><div><h3 class="title">
1.128 rillig 147: <a name="creating.python-module"></a>12.1.2. Python modules and programs</h3></div></div></div>
1.17 imil 148: <p>Python modules and programs packages are easily created using a
149: set of predefined variables.</p>
150: <p>
1.63 wiz 151: If some Python versions are not supported by the software, set the
152: <code class="varname">PYTHON_VERSIONS_INCOMPATIBLE</code> variable to the Python versions
153: that are not supported, e.g.
1.17 imil 154: </p>
155: <pre class="programlisting">
1.93 sevan 156: PYTHON_VERSIONS_INCOMPATIBLE= 27
1.17 imil 157: </pre>
158: <p>
1.103 wiz 159: If the packaged software is a Python module, include one of
160: <code class="filename">../../lang/python/egg.mk</code>,
161: <code class="filename">../../lang/python/distutils.mk</code>, or
162: <code class="filename">../../lang/python/extension.mk</code>.</p>
163: <p>Most Python packages use either <span class="quote">“<span class="quote">distutils</span>”</span> or
164: easy-setup/setuptools (<span class="quote">“<span class="quote">eggs</span>”</span>).
165: if the packaged software is using setuptools, you only need
166: to include <span class="quote">“<span class="quote"><code class="filename">../../lang/python/egg.mk</code></span>”</span>.
167: Otherwise, if the software uses <span class="quote">“<span class="quote">distutils</span>”</span>, include
168: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/distutils.mk</code></span>”</span>.
169: so pkgsrc will use this framework.
170: <span class="quote">“<span class="quote">distutils</span>”</span> uses a script called <code class="filename">setup.py</code>,
171: if the <span class="quote">“<span class="quote">distutils</span>”</span> driver is not called
172: <code class="filename">setup.py</code>, set the <code class="varname">PYSETUP</code> variable
173: to the name of the script.</p>
174: <p>Either way, the package directory should be called
1.24 wiz 175: <span class="quote">“<span class="quote">py-software</span>”</span> and <code class="varname">PKGNAME</code> should be set to
176: <span class="quote">“<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>”</span>, e.g.
1.17 imil 177: </p>
178: <pre class="programlisting">
179: DISTNAME= foopymodule-1.2.10
180: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
181: </pre>
1.63 wiz 182: <p>If it is an application, include
183: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>”</span>.
184: In order to correctly set the path to the Python interpreter, use the
1.17 imil 185: <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
1.36 wiz 186: (paths relative to <code class="varname">WRKSRC</code>) that must be corrected.
1.63 wiz 187: For example:
1.17 imil 188: </p>
189: <pre class="programlisting">
1.36 wiz 190: REPLACE_PYTHON= *.py
1.17 imil 191: </pre>
1.63 wiz 192: <p>Some Python modules have separate distributions for Python-2.x
193: and Python-3.x support. In pkgsrc this is handled by the
194: <code class="filename">versioned_dependencies.mk</code> file. Set
195: <code class="varname">PYTHON_VERSIONED_DEPENDENCIES</code> to the list of
196: packages that should be depended upon and include
197: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/versioned_dependencies.mk</code></span>”</span>,
198: then the pkgsrc infrastructure will depend on the appropriate package
199: version. For example:
200: </p>
201: <pre class="programlisting">
1.125 wiz 202: PYTHON_VERSIONED_DEPENDENCIES=dialog
1.63 wiz 203: </pre>
204: <p>
205: Look inside <code class="filename">versioned_dependencies.mk</code> for a list
206: of supported packages.</p>
1.17 imil 207: </div>
1.1 dsieger 208: </div>
1.42 asau 209: <div class="sect1">
1.1 dsieger 210: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.128 rillig 211: <a name="creating.examples"></a>12.2. Examples</h2></div></div></div>
1.42 asau 212: <div class="sect2">
1.1 dsieger 213: <div class="titlepage"><div><div><h3 class="title">
1.128 rillig 214: <a name="creating.nvu"></a>12.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div>
1.42 asau 215: <div class="sect3">
1.1 dsieger 216: <div class="titlepage"><div><div><h4 class="title">
1.128 rillig 217: <a name="creating.nvu.init"></a>12.2.1.1. The initial package</h4></div></div></div>
1.1 dsieger 218: <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
1.24 wiz 219: that the <span class="quote">“<span class="quote">nvu</span>”</span> package has not yet been imported into
1.1 dsieger 220: pkgsrc. As the description says it has to do with the web, the obvious
1.24 wiz 221: choice for the category is <span class="quote">“<span class="quote">www</span>”</span>.</p>
1.1 dsieger 222: <pre class="programlisting">
223: <code class="prompt">$</code> mkdir www/nvu
224: <code class="prompt">$</code> cd www/nvu
225: </pre>
226: <p>The web site says that the sources are available as a tar file, so
1.10 hubertf 227: I fed that URL to the <span class="command"><strong>url2pkg</strong></span> program:</p>
1.1 dsieger 228: <pre class="programlisting">
229: <code class="prompt">$</code> url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
230: </pre>
231: <p>My editor popped up, and I added a <code class="varname">PKGNAME</code> line
232: below the <code class="varname">DISTNAME</code> line, as the package name should
1.24 wiz 233: not have the word <span class="quote">“<span class="quote">sources</span>”</span> in it. I also filled in the
1.1 dsieger 234: <code class="varname">MAINTAINER</code>, <code class="varname">HOMEPAGE</code> and
235: <code class="varname">COMMENT</code> fields. Then the package
236: <code class="filename">Makefile</code> looked like that:</p>
237: <pre class="programlisting">
1.121 sevan 238: # $NetBSD $
1.1 dsieger 239: #
240:
241: DISTNAME= nvu-1.0-sources
242: PKGNAME= nvu-1.0
243: CATEGORIES= www
244: MASTER_SITES= http://cvs.nvu.com/download/
245: EXTRACT_SUFX= .tar.bz2
246:
247: MAINTAINER= rillig@NetBSD.org
248: HOMEPAGE= http://cvs.nvu.com/
249: COMMENT= Web Authoring System
250:
251: # url2pkg-marker (please do not remove this line.)
252: .include "../../mk/bsd.pkg.mk"
253: </pre>
1.123 wiz 254: <p>On the first line of output above, an artificial space has been added between NetBSD and $,
1.121 sevan 255: this is a workaround to prevent CVS expanding to the filename of the
256: guide.</p>
1.1 dsieger 257: <p>Then, I quit the editor and watched pkgsrc downloading a large
258: source archive:</p>
259: <pre class="programlisting">
260: url2pkg> Running "make makesum" ...
261: => Required installed package digest>=20010302: digest-20060826 found
262: => Fetching nvu-1.0-sources.tar.bz2
263: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
264: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
265: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
266: url2pkg> Running "make extract" ...
267: => Required installed package digest>=20010302: digest-20060826 found
268: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
269: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
270: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
271: ===> Installing dependencies for nvu-1.0
272: ===> Overriding tools for nvu-1.0
273: ===> Extracting for nvu-1.0
274: url2pkg> Adjusting the Makefile.
275:
276: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
277:
278: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
279: </pre>
280: </div>
1.42 asau 281: <div class="sect3">
1.1 dsieger 282: <div class="titlepage"><div><div><h4 class="title">
1.128 rillig 283: <a name="creating.nvu.problems"></a>12.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div>
1.1 dsieger 284: <p>Now that the package has been extracted, let's see what's inside
285: it. The package has a <code class="filename">README.txt</code>, but that only
286: says something about mozilla, so it's probably useless for seeing what
287: dependencies this package has. But since there is a GNU configure script
288: in the package, let's hope that it will complain about everything it
289: needs.</p>
290: <pre class="programlisting">
291: <code class="prompt">$</code> bmake
292: => Required installed package digest>=20010302: digest-20060826 found
293: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
294: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
295: ===> Patching for nvu-1.0
296: ===> Creating toolchain wrappers for nvu-1.0
297: ===> Configuring for nvu-1.0
298: [...]
299: configure: error: Perl 5.004 or higher is required.
300: [...]
301: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
302: [...]
303: </pre>
304: <p>That worked quite well. So I opened the package Makefile in my
305: editor, and since it already has a <code class="varname">USE_TOOLS</code> line, I
1.24 wiz 306: just appended <span class="quote">“<span class="quote">perl</span>”</span> to it. Since the dependencies of the
1.1 dsieger 307: package have changed now, and since a perl wrapper is automatically
1.24 wiz 308: installed in the <span class="quote">“<span class="quote">tools</span>”</span> phase, I need to build the package
1.1 dsieger 309: from scratch.</p>
310: <pre class="programlisting">
311: <code class="prompt">$</code> bmake clean
312: ===> Cleaning for nvu-1.0
313: <code class="prompt">$</code> bmake
314: [...]
315: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
316: GNU Make. You will not be able to build Mozilla without GNU Make.
317: [...]
318: </pre>
1.24 wiz 319: <p>So I added <span class="quote">“<span class="quote">gmake</span>”</span> to the
1.1 dsieger 320: <code class="varname">USE_TOOLS</code> line and tried again (from scratch).</p>
321: <pre class="programlisting">
322: [...]
323: checking for GTK - version >= 1.2.0... no
324: *** Could not run GTK test program, checking why...
325: [...]
326: </pre>
327: <p>Now to the other dependencies. The first question is: Where is the
328: GTK package hidden in pkgsrc?</p>
329: <pre class="programlisting">
330: <code class="prompt">$</code> echo ../../*/gtk*
331: [many packages ...]
332: <code class="prompt">$</code> echo ../../*/gtk
333: ../../x11/gtk
334: <code class="prompt">$</code> echo ../../*/gtk2
335: ../../x11/gtk2
336: <code class="prompt">$</code> echo ../../*/gtk2/bui*
337: ../../x11/gtk2/buildlink3.mk
338: </pre>
339: <p>The first try was definitely too broad. The second one had exactly
340: one result, which is very good. But there is one pitfall with GNOME
341: packages. Before GNOME 2 had been released, there were already many
342: GNOME 1 packages in pkgsrc. To be able to continue to use these
343: packages, the GNOME 2 packages were imported as separate packages, and
1.24 wiz 344: their names usually have a <span class="quote">“<span class="quote">2</span>”</span> appended. So I checked
1.1 dsieger 345: whether this was the case here, and indeed it was.</p>
346: <p>Since the GTK2 package has a <code class="filename">buildlink3.mk</code>
347: file, adding the dependency is very easy. I just inserted an
348: <code class="literal">.include</code> line before the last line of the package
349: <code class="filename">Makefile</code>, so that it now looks like this:</p>
350: <pre class="programlisting">
351: [...]
352: .include "../../x11/gtk2/buildlink3.mk"
353: .include "../../mk/bsd.pkg.mk
354: </pre>
1.10 hubertf 355: <p>After another <span class="command"><strong>bmake clean && bmake</strong></span>, the answer
1.1 dsieger 356: was:</p>
357: <pre class="programlisting">
358: [...]
359: checking for gtk-config... /home/roland/pkg/bin/gtk-config
360: checking for GTK - version >= 1.2.0... no
361: *** Could not run GTK test program, checking why...
362: *** The test program failed to compile or link. See the file config.log for the
363: *** exact error that occured. This usually means GTK was incorrectly installed
364: *** or that you have moved GTK since it was installed. In the latter case, you
365: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
366: configure: error: Test for GTK failed.
367: [...]
368: </pre>
1.24 wiz 369: <p>In this particular case, the assumption that <span class="quote">“<span class="quote">every package
370: prefers GNOME 2</span>”</span> had been wrong. The first of the lines above
1.1 dsieger 371: told me that this package really wanted to have the GNOME 1 version of
372: GTK. If the package had looked for GTK2, it would have looked for
1.10 hubertf 373: <span class="command"><strong>pkg-config</strong></span> instead of <span class="command"><strong>gtk-config</strong></span>.
1.1 dsieger 374: So I changed the <code class="literal">x11/gtk2</code> to
375: <code class="literal">x11/gtk</code> in the package <code class="filename">Makefile</code>,
376: and tried again.</p>
377: <pre class="programlisting">
378: [...]
1.59 jnemeth 379: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
1.1 dsieger 380: In file included from xpidl.c:42:
381: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
382: In file included from xpidl.c:42:
383: xpidl.h:132: error: parse error before "IDL_ns"
384: [...]
385: </pre>
386: <p>The package still does not find all of its dependencies. Now the
387: question is: Which package provides the
388: <code class="filename">libIDL/IDL.h</code> header file?</p>
389: <pre class="programlisting">
390: <code class="prompt">$</code> echo ../../*/*idl*
391: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
392: <code class="prompt">$</code> echo ../../*/*IDL*
393: ../../net/libIDL
394: </pre>
395: <p>Let's take the one from the second try. So I included the
396: <code class="filename">../../net/libIDL/buildlink3.mk</code> file and tried
397: again. But the error didn't change. After digging through some of the
398: code, I concluded that the build process of the package was broken and
399: couldn't have ever worked, but since the Mozilla source tree is quite
400: large, I didn't want to fix it. So I added the following to the package
401: <code class="filename">Makefile</code> and tried again:</p>
402: <pre class="programlisting">
403: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
1.127 leot 404: BUILDLINK_TRANSFORM+= l:IDL:IDL-2
1.1 dsieger 405: </pre>
406: <p>The latter line is needed because the package expects the library
407: <code class="filename">libIDL.so</code>, but only
408: <code class="filename">libIDL-2.so</code> is available. So I told the compiler
409: wrapper to rewrite that on the fly.</p>
410: <p>The next problem was related to a recent change of the FreeType
1.126 leot 411: interface. I looked up in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/seamonkey/README.html" target="_top"><code class="filename">www/seamonkey</code></a>
1.1 dsieger 412: which patch files were relevant for this issue and copied them to the
413: <code class="filename">patches</code> directory. Then I retried, fixed the
414: patches so that they applied cleanly and retried again. This time,
415: everything worked.</p>
416: </div>
1.42 asau 417: <div class="sect3">
1.1 dsieger 418: <div class="titlepage"><div><div><h4 class="title">
1.128 rillig 419: <a name="creating.nvu.inst"></a>12.2.1.3. Installing the package</h4></div></div></div>
1.1 dsieger 420: <pre class="programlisting">
421: <code class="prompt">$</code> bmake CHECK_FILES=no install
422: [...]
423: <code class="prompt">$</code> bmake print-PLIST >PLIST
424: <code class="prompt">$</code> bmake deinstall
425: <code class="prompt">$</code> bmake install
426: </pre>
427: </div>
428: </div>
429: </div>
430: </div>
431: <div class="navfooter">
432: <hr>
433: <table width="100%" summary="Navigation footer">
434: <tr>
435: <td width="40%" align="left">
1.128 rillig 436: <a accesskey="p" href="help-devel.html">Prev</a> </td>
1.1 dsieger 437: <td width="20%" align="center"><a accesskey="u" href="developers-guide.html">Up</a></td>
438: <td width="40%" align="right"> <a accesskey="n" href="components.html">Next</a>
439: </td>
440: </tr>
441: <tr>
1.128 rillig 442: <td width="40%" align="left" valign="top">Chapter 11. Getting help </td>
1.1 dsieger 443: <td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
1.128 rillig 444: <td width="40%" align="right" valign="top"> Chapter 13. Package components - files, directories and contents</td>
1.1 dsieger 445: </tr>
446: </table>
447: </div>
448: </body>
449: </html>
CVSweb <webmaster@jp.NetBSD.org>