[Mesa-dev] [android-x86-devel] [RFC 0/7] android: enable llvmpipe for software rendering

[Jose Fonseca]

On 28/04/16 20:53, Rob Herring wrote:
> On Thu, Apr 28, 2016 at 1:57 PM, Jose Fonseca <jfonseca at vmware.com> wrote:
>> On 28/04/16 19:50, Rob Herring wrote:
>>>
>>> On Thu, Apr 28, 2016 at 12:35 PM, Roland Scheidegger <sroland at vmware.com>
>>> wrote:
>>>>
>>>> Am 28.04.2016 um 17:52 schrieb Chih-Wei Huang:
>>>>>
>>>>> I clearly understand this point.
>>>>> Actually I've spent several days to try to
>>>>> make it work on the master branch.
>>>>> That's why it was delayed -- I supposed to send them
>>>>> in the last week.
>>>>>>
>>>>>> However, the master branch is always broken for android.
>>>>>
>>>>> There are a lot of build break I need to fix and workaround
>>>>> or I can't test it. After fixed all the errors and built it OK,
>>>>> however, it didn't work as expected.
>>>>> The system boots to Home but all display is garbled.
>>>>> I'm not sure if I made some mistakes on
>>>>> fixing the building errors or there are some changes
>>>>> that really broke these patches.
>>>>> (the latest commit I've tried in the master is 32cb7d61)
>>>>> I finally decide to give it up and send them as the current status.
>>>>> (otherwise it will take too much of my time and delay
>>>>> my other pending tasks)
>>>>>
>>>>> Unfortunately the situation is most mesa developers
>>>>> don't care android so they usually break android build
>>>>> or functions. Unless the situation is changed it's very hard
>>>>> for us to follow the master branch closely.
>>>>
>>>>
>>>> I suppose if it's possible to set up some build bot for it which sends
>>>> out emails complaining when it breaks that would help with the build
>>>> failures.
>>>
>>>
>>> I have that in my plans, but it is not there yet. I'm updating to
>>> master at least weekly and fixing things, but new breakage seems to
>>> happen faster than getting fixes committed. I'm usually the one fixing
>>> the breakage. Given most people don't have an Android tree, having
>>> them fix build problems is not all that realistic. I'll happily test
>>> the fixes though.
>>>
>>> BTW, the latest break is from "i965/fs_surface_builder: Add a helper
>>> for converting GL to ISL formats."
>>>
>>> Rob
>>
>>
>> Is using autotools or SCons for Android really impossible?
>
> I looked into autotools and there are some tools to help with using
> them for Android builds. They don't look too active and I'd guess
> you'd replace screwing with the Android.mk with screwing with the
> tool. I know nothing about SCons, but had the impression it breaks
> frequently too.

SCons might break now and then, but the difference is that it's not left 
broken for long periods.

Anyway, the more overlap with the existing build systems the less likely 
it breaks.

For example, sharing Makefiles.sources between SCons and autotools 
greatly reduced the breakage (on both directions.)

> Seems like the Google folks are up to something with the autotools, so
> may be they have some solution in the works.

Let's hope so.

Jose