Getting apitrace to work on Android
george at mozilla.com
Thu Mar 8 18:59:08 PST 2012
On 8 Mar 2012, at 20:50, Zack Rusin wrote:
> Cool. FWIW, ApiTrace has already been made to work on Android by the LunarG
> folks. I'm ccing Chia-I Wu to see if he wants to say anything about it.
> From my side, I really dislike the #if android's and the cmake patches are
> very ugly. Also importing GL headers to compile a GL application used to debug
> GL applications seems at best crazy.
> But I have very little time for fun projects nowadays and I'm sure Jose will
> do a proper review when he'll be back from his vacations.
I also dislike ifdefs, but for such small changes I'm not sure which is worse - ifdefing the small changes, or putting said functions in Android-specific files.
I tried to make the cmake changes as uninvasive as possible. Can you suggest how to clean it up - I'm not sure what your specific concerns are.
When I spoke to Jose about the GL headers being imported he suggested that this way was the best way to deal with the issue of apitrace supporting several different GL APIs for tracing at runtime, but no way at choose at compile time which ones to compile in. I originally looked into getting apitrace to only build certain APIs like GLES2 at compile time but it proved to be a huge undertaking and I was on a time budget… Do you have any other possibilities for how to deal with this problem?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the apitrace