generic-poky/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-autotools.html

53 lines
3.3 KiB
HTML
Raw Normal View History

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>7.2.<2E>Autotooled Packages - autotools.bbclass</title>
<link rel="stylesheet" type="text/css" href="../book.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
<link rel="up" href="ref-classes.html" title="Chapter<65>7.<2E>Classes">
<link rel="prev" href="ref-classes-base.html" title="7.1.<2E>The base class - base.bbclass">
<link rel="next" href="ref-classes-update-alternatives.html" title="7.3.<2E>Alternatives - update-alternatives.bbclass">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.2.<2E>Autotooled Packages - autotools.bbclass">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="ref-classes-autotools"></a>7.2.<2E>Autotooled Packages - <code class="filename">autotools.bbclass</code>
</h2></div></div></div>
<p>
Autotools (<code class="filename">autoconf</code>, <code class="filename">automake</code>,
and <code class="filename">libtool</code>) bring standardization.
This class defines a set of tasks (configure, compile etc.) that
work for all Autotooled packages.
It should usually be enough to define a few standard variables
and then simply <code class="filename">inherit autotools</code>.
This class can also work with software that emulates Autotools.
For more information, see the
"<a class="link" href="../dev-manual/usingpoky-extend-addpkg-autotools.html" target="_self">Autotooled Package</a>"
section in the Yocto Project Development Manual.
</p>
<p>
It's useful to have some idea of how the tasks defined by this class work
and what they do behind the scenes.
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p><code class="filename">do_configure</code> &#8208; regenerates the
configure script (using <code class="filename">autoreconf</code>) and then launches it
with a standard set of arguments used during cross-compilation.
You can pass additional parameters to <code class="filename">configure</code> through the
<code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OECONF" title="EXTRA_OECONF">EXTRA_OECONF</a></code> variable.
</p></li>
<li class="listitem"><p><code class="filename">do_compile</code> &#8208; runs <code class="filename">make</code> with
arguments that specify the compiler and linker.
You can pass additional arguments through
the <code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OEMAKE" title="EXTRA_OEMAKE">EXTRA_OEMAKE</a></code> variable.
</p></li>
<li class="listitem"><p><code class="filename">do_install</code> &#8208; runs <code class="filename">make install</code>
and passes a DESTDIR option, which takes its value from the standard
<code class="filename"><a class="link" href="ref-variables-glos.html#var-DESTDIR" title="DESTDIR">DESTDIR</a></code> variable.
</p></li>
</ul></div>
<p>
</p>
</div></body>
</html>