From: Lorn Potter <lpotter@trolltech.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: How should OE be used?
Date: Tue, 25 Sep 2007 04:48:40 +1000 [thread overview]
Message-ID: <46F80688.2020702@trolltech.com> (raw)
In-Reply-To: <46F587F7.4060501@balister.org>
I have always thought that oe needed an easier way to choose packages,
like buildroot.
Some gui that can edit all the conf's and task's, and image.bb's
painlessly and easily would make a tom of difference.
The learning curve for oe is too high.
Take buildroot, for example. A person can download it, run make
menuconfig, set up the system, arch, and select packages, all in one go.
You do not need to know that you should have to either edit or create
your own tasks, or image .bb's, much less the syntax for those files.
--
Lorn 'ljp' Potter
Software Engineer, Systems Group, MES, Trolltech
next prev parent reply other threads:[~2007-09-24 18:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 21:24 How should OE be used? Philip Balister
2007-09-23 11:19 ` Leon Woestenberg
2007-09-23 12:33 ` Koen Kooi
2007-09-24 17:20 ` Tim Bird
2007-09-24 17:43 ` Koen Kooi
2007-09-24 18:01 ` Tim Bird
2007-09-24 15:55 ` Tim Bird
2007-09-24 16:35 ` Philip Balister
2007-09-24 17:14 ` Tim Bird
2007-09-24 18:04 ` Leon Woestenberg
2007-09-24 19:23 ` Koen Kooi
2007-09-24 14:48 ` Darcy Watkins
2007-09-25 12:19 ` Stelios Koroneos
2007-09-25 15:15 ` Koen Kooi
2007-09-25 20:54 ` Darcy Watkins
2007-09-24 16:14 ` Cliff Brake
2007-09-24 18:36 ` Craig Hughes
2007-09-24 19:27 ` Philip Balister
2007-09-24 21:37 ` Richard Purdie
2007-09-24 18:48 ` Lorn Potter [this message]
2007-09-24 19:01 ` Craig Hughes
2007-09-24 19:39 ` Lorn Potter
2007-09-24 20:33 ` Craig Hughes
2007-09-24 20:52 ` Richard Purdie
2007-09-24 21:11 ` Lorn Potter
2007-09-24 22:35 ` Richard Purdie
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=46F80688.2020702@trolltech.com \
--to=lpotter@trolltech.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.