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] [RFC PATCH 0/10] add new virtual-package infrastructure
Date: Wed, 26 Feb 2014 19:03:38 +0100	[thread overview]
Message-ID: <20140226180338.GA3348@free.fr> (raw)
In-Reply-To: <CAB0FRssWBtzFimD0JShSj8Y7efvUWk4Ono_cgSxqw0uMLk0PTg@mail.gmail.com>

Fran?ois, All,

On 2014-02-26 09:23 +0100, Fran?ois Perrad spake thusly:
> 2014-02-25 23:02 GMT+01:00 Yann E. MORIN <yann.morin.1998@free.fr>:
> > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Here is a quick series implementing a new infrastructure for virtual
> > packages.
> could you check your new infrastructure with these 2 patches :
>  http://patchwork.ozlabs.org/patch/323464/
>  http://patchwork.ozlabs.org/patch/323465/
> because for the first time, a virtual package is used on host and target side.

This was just a quick proof-of-concept implementation, mostly targeted
at getting some feedback on the global idea.

I based this ontop of master because I forgot to checkout next first,
and rebasing ontop of -next uncovered some merge conflicts, so I just
aborted the rebase. It will need a bit of love before it is ready.

So, yes, it may be impacted by patches applied on -next, or even patches
pending in Patchwork.

> Note that the definition of LUAINTERPRETER_SOURCE is not enough,
> the definition of HOST_LUAINTERPRETER_SOURCE is required too.

Ah, so we will need to handle the case for host-virtual-packages, too?
I just did not bother doign so for this first rough draft.

Thanks for the report! :-)

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.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2014-02-26 18:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 22:02 [Buildroot] [RFC PATCH 0/10] add new virtual-package infrastructure Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 01/10] package/lua: rename config options Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 02/10] packages: add infrastructure for virtual packages Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 03/10] package/powervr: convert to the virtual-package infrastructure Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 04/10] package/libgles: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 05/10] package/libegl: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 06/10] package/libopenmax: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 07/10] package/libopenvg: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 08/10] package/luainterpreter: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 09/10] package/jpeg: " Yann E. MORIN
2014-02-25 22:02 ` [Buildroot] [PATCH 10/10] package/cryptodev: " Yann E. MORIN
2014-02-26  8:23 ` [Buildroot] [RFC PATCH 0/10] add new " François Perrad
2014-02-26 17:39   ` Arnout Vandecappelle
2014-02-26 18:03   ` Yann E. MORIN [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=20140226180338.GA3348@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