From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Minimal BitBake template
Date: Wed, 16 Jan 2013 12:54:09 +0000 [thread overview]
Message-ID: <1358340849.12628.0.camel@ted> (raw)
In-Reply-To: <50F41A7D.7080108@codesourcery.com>
On Mon, 2013-01-14 at 14:47 +0000, Andrew Stubbs wrote:
> On 14/01/13 14:23, Bill Traynor wrote:
> > This doesn't answer your problem directy, and you may have seen this
> > tutorial already, but in case not:
> >
> > http://hambedded.org/blog/2012/11/24/from-bitbake-hello-world-to-an-image/
> >
> > Note that I'm including a hello world example in the new BitBake User
> > Manual I'm working on.
>
> Thanks! That's a very useful resource. :)
>
> It's surprisingly hard to find BitBake tutorials that do not assume that
> one is trying to insert something into OE. I wish I'd found this sooner.
>
> The other think I wish I'd found sooner, that you page references, are
> the example conf and bbclass files inside the bitbake sources. I had
> assumed they were some sort of internal detail, and not for the likes of me.
>
> Apparently my base.bbclass and hello.bb files are absolutely fine, but
> something, as yet unidentified, in the bitbake.conf from the sources has
> fixed my problem.
At a guess, did you set the STAMP variable?
We could certainly make bitbake give less obtuse errors if some of the
key variables aren't set. Its not been a priority since people don't do
that very often though...
Cheers,
Richard
prev parent reply other threads:[~2013-01-16 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 14:04 Minimal BitBake template Andrew Stubbs
2013-01-14 14:23 ` Bill Traynor
2013-01-14 14:47 ` Andrew Stubbs
2013-01-16 12:54 ` Richard Purdie [this message]
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=1358340849.12628.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=ams@codesourcery.com \
--cc=bitbake-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.