Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] manual: add virtual package tutorial.
Date: Sun, 23 Feb 2014 20:04:07 +0100	[thread overview]
Message-ID: <20140223190407.GE32759@free.fr> (raw)
In-Reply-To: <20140219141950.GA25812@pc-eric>

Eric, All,

On 2014-02-19 15:19 +0100, Eric Le Bihan spake thusly:
> On Tue, Feb 18, 2014 at 09:34:41PM +0100, Samuel Martin wrote:
> [...]
> > > +[[virtual-package-tutorial]]
> > > +How to add a virtual package
> > > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > +
> > > +In Buildroot, a virtual package is a package whose functionalities are
> > > +provided by one or more packages, referred to as 'providers'.
> > > +
> > > +For example, 'OpenGL ES' is an API for 2D and 3D graphics on embedded systems.
> > > +The implementation of this API is different for the 'Allwinner Tech Sunxi' and
> > > +the 'Texas Instruments OMAP35xx' plaftorms. So +libgles+ will be a virtual
> > > +package and +sunxi-mali+ and +ti-gfx+ will be the providers.
> >
> > The generic way of presenting the virtual/provider "infra" in Buildroot is:
> > we want to use the virtual/provider infrastructure when there is one
> > API, but several packages implementing this API, so we want an
> > extensible mechanism allowing to choose what implementation we want in
> > the target rootfs.
> I will update the text in order to put emphasis on this idea.

How are your changes going?

There are quite a few improvements to the manual being upstreamed. Your
changes would make for another nice addition.

Do you think you could resubmit sometime next week, so this has a chance
to go in before the release?

Thanks for your work on this! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-02-23 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 15:11 [Buildroot] [PATCH v2 1/1] manual: add virtual package tutorial Eric Le Bihan
2014-02-17 17:19 ` Arnout Vandecappelle
2014-02-18 11:44   ` Eric Le Bihan
2014-02-18 12:03     ` Arnout Vandecappelle
2014-02-18 20:34 ` Samuel Martin
2014-02-19 14:19   ` Eric Le Bihan
2014-02-23 19:04     ` Yann E. MORIN [this message]
2014-02-24 10:00       ` Eric Le Bihan

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=20140223190407.GE32759@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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