From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "William M.A. Traynor" <wmat@alphatroop.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Hello World example for BitBake Manual
Date: Thu, 30 May 2013 18:11:56 +0100 [thread overview]
Message-ID: <3360241.lzjhbPNm27@helios> (raw)
In-Reply-To: <CAGfZjq7x_OAHRw-_S8Rm0mZRa793dmnp36mpPCbTw18zvNKhEA@mail.gmail.com>
On Wednesday 29 May 2013 13:28:11 William M.A. Traynor wrote:
> In researching and trying to work through a Hello World example for
> inclusion in the BitBake Manual, I've been able to reproduce the
> examples described in the following thread:
> http://www.mail-archive.com/yocto@yoctoproject.org/msg09347.html
I think this example is generic enough for the documentation.
> and in the following blog post:
> http://hambedded.org/blog/2012/11/24/from-bitbake-hello-world-to-an-image/
This however, whilst it is a very detailed and well written explanation, goes
a bit further and is trying to put something together that's moving a bit
towards what OE does, as an aid to explain how OE works (e.g. the introduction
of an "autotools.bbclass"). I'm not sure this is really appropriate for the
Bitbake manual IMHO. You could draw inspiration from parts of it though.
> Does anyone have sufficient knowledge of each of these examples to
> comment whether they're "generic" enough for the manual? I'm trying
> my best to keep content as generic as possible, but it's proving to be
> a struggle at times.
>
> Specifically, I'm finding that it's possible to be to generic, and
> thereby not adequately demonstrate the power of the tool.
I know, it can be tricky. If you have specific areas you'd like help on then
I'm more than happy to help though.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-30 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 17:28 Hello World example for BitBake Manual William M.A. Traynor
2013-05-30 17:11 ` Paul Eggleton [this message]
2013-05-30 17:24 ` William M.A. Traynor
2013-05-30 19:08 ` Eren Türkay
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=3360241.lzjhbPNm27@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=wmat@alphatroop.com \
/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.