From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Debugging OpenEmbedded Builds
Date: Tue, 27 Sep 2011 17:04:21 +0200 [thread overview]
Message-ID: <4E81E5F5.8080603@freyther.de> (raw)
In-Reply-To: <4E81B106.8040801@tu-braunschweig.de>
On 09/27/2011 01:18 PM, Christian Keck wrote:
> How can debug an OpenEmbedded build? I have made some changes to a board file,
> but it seems that my changes have no effect. Is there a opportunity to look
> into source code just before they are compiled?
you can use bitbake -e recipe, to see how variables and scripts that will be
executed look like. also it generates scripts in the temp/ dir in WORKDIR that
can be inspected, also bitbake -c devshell NAME gets you into such an environment.
next prev parent reply other threads:[~2011-09-27 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 11:18 Debugging OpenEmbedded Builds Christian Keck
2011-09-27 15:04 ` Holger Freyther [this message]
2011-10-07 9:42 ` Alex J Lennon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E81E5F5.8080603@freyther.de \
--to=holger+oe@freyther.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox