From: Holger Hans Peter Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Working with OEMs
Date: Sat, 6 Feb 2010 20:12:36 +0100 [thread overview]
Message-ID: <201002062012.36110.holger+oe@freyther.de> (raw)
In-Reply-To: <C791CD9B.22735%jgrant@vml.com>
On Friday 05 February 2010 20:28:59 Jeremy Grant wrote:
Hi Jeremy,
in general we encourage people to use one of the existing distributions
(angstrom, micro, minimal). In some recipes these distro's have done
configuration or other policy. This is done with the "OVERRIDE" system of
bitbake which is working by name. So just copying angstrom.conf to a new name
will most likely not work right a way.
For the next part. I would suggest creating a "task-oem-kind" and a "oem-kind-
image" which would install Qt Embedded 4.6, the required plugins and
additional applications like the arora browser.
My general suggestion is to use OE only for the tasks it is good. E.g. if you
force a developer to use it for application development it can be pretty
painful on both sides.
At the OEM I would encourage someone to write the machine config, makes sure
the init files are working. As the output of the OEM they should have the
machine file, the sourcecode, a bootable image, and the result of something
like "meta-toolchain-qte" or "meta-toolchain" to allow easy application
development for the target hardware.
holger
next prev parent reply other threads:[~2010-02-06 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 19:28 Working with OEMs Jeremy Grant
2010-02-06 19:12 ` Holger Hans Peter Freyther [this message]
2010-02-08 16:48 ` C Michael Sundius
2010-02-08 18:37 ` Philip Balister
2010-02-09 17:56 ` C Michael Sundius
2010-02-09 21:47 ` Michael Smith
2010-02-09 22:33 ` Peter Chubb
2010-02-09 23:23 ` C Michael Sundius
2010-02-09 23:01 ` C Michael Sundius
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=201002062012.36110.holger+oe@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 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.