From: Rob Herring <robh@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Rob Clark <robdclark@chromium.org>,
Jiyong Park <jiyong@google.com>,
Robert Foss <robert.foss@collabora.com>,
Mauro Rossi <issor.oruam@gmail.com>,
Alistair Strachan <astrachan@google.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Eric Anholt <anholt@google.com>,
Sean Paul <seanpaul@chromium.org>,
Dan Willemsen <dwillemsen@google.com>,
Emil Velikov <emil.velikov@collabora.com>,
Vishal Bhoj <vishal.bhoj@linaro.org>
Subject: Re: [PATCH] libdrm: Convert to Android.mk to Android.bp
Date: Tue, 24 Sep 2019 17:24:01 -0500 [thread overview]
Message-ID: <CAL_JsqLR212Et5Z82Gr=DJfB5WY-4o8bN_s5peu07EnaEVEOYQ@mail.gmail.com> (raw)
In-Reply-To: <20190924212920.76103-1-john.stultz@linaro.org>
On Tue, Sep 24, 2019 at 4:29 PM John Stultz <john.stultz@linaro.org> wrote:
>
> This patch removes the deprecated Android.mk files and replaces
> them with Android.bp files, used in Android N and newer
> releases.
>
> This is needed in order to build libdrm/master against recent
> Android releases and AOSP/master, as some of the Treble build
> options required since Android O cannot be expressed in
> Andorid.mk files.
>
> Patch originally by Dan Willemsen with fixes folded in by:
> Jerry Zhang, Eliott Hughes and myself.
>
> While this does cost comptability with older pre Android N
> releases, I'd contend that being able to build/test
> libdrm/master against AOSP/master and recent releases is more
> valuable then soley maintaining support for old and unsupported
> Android releases.
Trying to maintain something that works across more than 3 releases or
so is painful. I don't think android-x86 folks have the bandwidth to
maintain things older than that *and* update to newer versions. So I
think only supporting the n latest releases is good.
Are .bp files for master/Q compatible back to N (or O)? IIRC, at least
for the first couple of releases with .bp files, they seemed to have
incompatible changes.
Rob
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-24 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 21:29 [PATCH] libdrm: Convert to Android.mk to Android.bp John Stultz
2019-09-24 21:51 ` Robert Foss
2019-09-24 22:24 ` Rob Herring [this message]
2019-09-24 23:30 ` John Stultz
2019-09-25 6:09 ` John Stultz
2019-09-25 10:39 ` Eric Engestrom
2019-09-25 15:00 ` Mauro Rossi
2019-09-25 16:17 ` John Stultz
2019-09-25 18:00 ` Mauro Rossi
2019-09-25 16:04 ` Rob Clark
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='CAL_JsqLR212Et5Z82Gr=DJfB5WY-4o8bN_s5peu07EnaEVEOYQ@mail.gmail.com' \
--to=robh@kernel.org \
--cc=anholt@google.com \
--cc=astrachan@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwillemsen@google.com \
--cc=emil.velikov@collabora.com \
--cc=issor.oruam@gmail.com \
--cc=jiyong@google.com \
--cc=john.stultz@linaro.org \
--cc=robdclark@chromium.org \
--cc=robert.foss@collabora.com \
--cc=seanpaul@chromium.org \
--cc=vishal.bhoj@linaro.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.