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 1/1] package/weston-imx: Split weston-imx off from weston
Date: Sun, 14 Jul 2019 20:53:25 +0200	[thread overview]
Message-ID: <20190714185325.GH29941@scaer> (raw)
In-Reply-To: <CADvTj4r+GiLH=1oA7c8OsTRhLnA+TPYHpgRbQmttt5Es0QObdQ@mail.gmail.com>

James, All,

On 2019-07-14 12:37 -0600, James Hilliard spake thusly:
> On Sun, Jul 14, 2019 at 12:34 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2019-06-25 16:50 -0600, James Hilliard spake thusly:
> > > This is in preparation for migration of weston to the meson build system.
> > > Since weston-imx is based off of a much older version of weston it is
> > > difficult to maintain as part of the weston package.
[--SNIP--]
> > Which implies that we should allow bioth westons to be installed side by
> > side, and that the imx variant be installed as 'weston-imx', e.g. using
> > the ./configure flag:
> Is there a use case for having both westons side by side?

Well, yes: the RDB stuff for example does not seem to depend on the
hardware at all, in fact, so it would be better if it were provided by
the real weston, which is more up-to-date with RDP than by the imx fork,
which supports an older version of RDP. And it has caused grief in the
past that when we update weston, it uses newer FreeRDP APIs, or the
other way around, when we update FreeRDP, it no longer exports APIs
needed by older weston.

So, I'd like we find a way for the imxc fork to be consrained to only
the actual imx backend, and keep using the official weston for all the
rest.

Regards,
Yann E. MORIN.

> >     --program-suffix=-imx
> >
> > Regards,
> > Yann E. MORIN.
> >
> > --
> > .-----------------.--------------------.------------------.--------------------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> > | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> > '------------------------------^-------^------------------^--------------------'

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

  reply	other threads:[~2019-07-14 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 22:50 [Buildroot] [PATCH 1/1] package/weston-imx: Split weston-imx off from weston James Hilliard
2019-06-26  3:58 ` Baruch Siach
2019-06-26  4:34   ` James Hilliard
2019-06-26 16:24     ` Gary Bisson
2019-06-26 16:50       ` James Hilliard
2019-07-14 18:34 ` Yann E. MORIN
2019-07-14 18:37   ` James Hilliard
2019-07-14 18:53     ` Yann E. MORIN [this message]
2019-07-14 19:04       ` James Hilliard

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=20190714185325.GH29941@scaer \
    --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