blob: c48b00e97ab4fcb7e69c3252d92c2cee5a905590 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2.3.3.�Dependency Graphs</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="usingpoky-debugging.html" title="2.3.�Debugging Build Failures">
<link rel="prev" href="usingpoky-debugging-taskrunning.html" title="2.3.2.�Running Specific Tasks">
<link rel="next" href="usingpoky-debugging-bitbake.html" title="2.3.4.�General BitBake Problems">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.3.�Dependency Graphs">
<div class="titlepage"><div><div><h3 class="title">
<a name="usingpoky-debugging-dependencies"></a>2.3.3.�Dependency Graphs</h3></div></div></div>
<p>
Sometimes it can be hard to see why BitBake wants to build some other packages before a given
package you have specified.
The <code class="filename">bitbake -g targetname</code> command creates the
<code class="filename">depends.dot</code>, <code class="filename">package-depends.dot</code>,
and <code class="filename">task-depends.dot</code> files in the current directory.
These files show the package and task dependencies and are useful for debugging problems.
You can use the <code class="filename">bitbake -g -u depexp targetname</code> command to
display the results in a more human-readable form.
</p>
</div></body>
</html>
|
