From: Gary Bisson <bisson.gary@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/weston-imx: Split weston-imx off from weston
Date: Wed, 26 Jun 2019 18:24:52 +0200 [thread overview]
Message-ID: <20190626162452.GA12049@t450s.lan> (raw)
In-Reply-To: <CADvTj4r9oO=KdternzH6hRnXW7m14KJgzzFYx+65dP=5F8Kvqg@mail.gmail.com>
Hi James, Baruch,
On Tue, Jun 25, 2019 at 10:34:34PM -0600, James Hilliard wrote:
> On Tue, Jun 25, 2019, 9:58 PM Baruch Siach <baruch@tkos.co.il> wrote:
>
> > Hi James,
> >
> > Adding Garry to Cc.
> >
> > On Tue, Jun 25, 2019 at 04:50:08PM -0600, James Hilliard wrote:
> > > 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.
> >
> > It might be easier to bump weston-imx to rel_imx_4.19.35_1.0.0 which is
> > based
> > on upstream version 6.0.0.
> >
> From what I could tell the imx features were only set up for autotools for
> that version as well.
Don't know much about meson to be honest but NXP patches indeed only
change configure.ac and not meson_options.txt.
If the switch to meson is happening now, yes I guess the NXP fork will
have to be split.
Also note that any update to the weston-imx version will imply using the
NXP-forked version of wayland-protocols as well [1] :(
Regards,
Gary
[1] https://source.codeaurora.org/external/imx/wayland-protocols-imx/log/?h=rel_imx_4.14.98_2.0.0_ga
next prev parent reply other threads:[~2019-06-26 16:24 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 [this message]
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
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=20190626162452.GA12049@t450s.lan \
--to=bisson.gary@gmail.com \
--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