[Mesa-dev] [RFC][PATCH 4/5] Android.mk: Add option to use vendor version of mesa

Harish Krupo harish.krupo.kps at intel.com
Wed Jul 25 12:48:13 UTC 2018


Emil Velikov <emil.l.velikov at gmail.com> writes:

> On 25 July 2018 at 00:21, John Stultz <john.stultz at linaro.org> wrote:
>> From: Yong Yao <yong.yao at intel.com>
>> This is a forward port of a patch from the AOSP/master branch:
>> https://android.googlesource.com/platform/external/mesa3d/+/b1e5fad1db4c1d51c7ae3a033b100a8429ae5415%5E%21/
>> Which allows boards to provide their own custom copy of mesa.
> Thanks for sorting these out John.
> My understanding was that when a custom project repo is used one
> handles that in the device manifest. Roughly as:
>  - foo.xml -> contains vast majority of the git repos with associated tags/etc
>  - local.xml -> removes any repo/project from ^^, adds new one
> Is that no longer the case, or I simply misremember how Android does things?

You do remember correctly. :)
Generally there is a default.xml which includes projects.xml and
remove.xml. Projects.xml contains all the <project... /> lines and the
remove.xml contains the <remove-project... /> lines to remove those
repos for that particular project.

Reference: https://github.com/projectceladon/manifest

Thank you
Harish Krupo

More information about the mesa-dev mailing list