blob: 06a3b7f9fac4a28c32e11853a0ac4d9878107148 (
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
27
28
29
30
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2.3.4.�General BitBake Problems</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-dependencies.html" title="2.3.3.�Dependency Graphs">
<link rel="next" href="usingpoky-debugging-buildfile.html" title="2.3.5.�Building with No Dependencies">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.4.�General BitBake Problems">
<div class="titlepage"><div><div><h3 class="title">
<a name="usingpoky-debugging-bitbake"></a>2.3.4.�General BitBake Problems</h3></div></div></div>
<p>
You can see debug output from BitBake by using the <code class="filename">-D</code> option.
The debug output gives more information about what BitBake
is doing and the reason behind it.
Each <code class="filename">-D</code> option you use increases the logging level.
The most common usage is <code class="filename">-DDD</code>.
</p>
<p>
The output from <code class="filename">bitbake -DDD -v targetname</code> can reveal why
BitBake chose a certain version of a package or why BitBake
picked a certain provider.
This command could also help you in a situation where you think BitBake did something
unexpected.
</p>
</div></body>
</html>
|
