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