[Mesa-dev] [PATCH] android: add megadriver_stub

Chad Versace chad.versace at linux.intel.com
Tue Oct 29 19:27:02 CET 2013


On 10/28/2013 04:29 PM, Emil Velikov wrote:
> On 28/10/13 08:07, Adrian Negreanu wrote:
>> From: Adrian Negreanu <adrian.m.negreanu at intel.com>
>>
>> Fixes linker error:
>>    ld: .../libmesa_dri_common_intermediates/libmesa_dri_common.a(dri_util.o):
>>    in function globalDriverAPI:dri_util.c(.data.rel+0x0): error: undefined
>>    reference to 'driDriverAPI'
>>
> Hi Adrian,
>
> To be honest, with dricore gone I was expecting bigger issues. From what
> I can see the only way to get around that(missing dricore) is to build
> without MESA_BUILD_CLASSIC (i.e. without i915 i965).
>
> Would you mind sharing some light and/or cleaning
> src/mesa/Android.libmesa_dricore.mk ?
>
> Additionally what can one do it he wishes to change/update parts of the
> Android build system?
>
> I've been trying to cleanup, and provide some symmetry to the three
> build systems, and I'm currently short of an Android setup.
>
> Is there a VM that can be used to at least compile test patches ? ...or
> a person/build bot that we can ping to compile/run test any changes?

Emil, there is no need to use a VM to build Android. The officially supported
OS for building Android is Ubuntu, but I've also had success with Fedora and
ArchLinux. A 64-bit OS is required. To get started, follow the Developer instructions
at [https://01.org/android-ia/documentation] and choose the lunch target 'core_mesa-eng'.
The Mesa sources are located at $ANDROID_TOP/external/mesa.

Adrian, does the resultant Android image work with this patch applied? I suspect
there may be issues because, as Emil observed, Android is still build and linking
libdricore into i965_dri.


More information about the mesa-dev mailing list