----- Original Message ----- > On Thu, Aug 4, 2011 at 2:47 AM, Chad Versace <c...@chad-versace.us> > wrote: > > This is the first step in porting libGLES* and libEGL to Android. > > > > The makefile doesn't build anything yet; it just defines common > > variables. > > > > The values for MESA_COMMON_C_FLAGS and MESA_COMMON_CPP_FLAGS, I > > obtained > > by invoking autogen.sh with the options below and then inspecting > > MESA_TOP/configs/autoconf. My immediate goal is to port i965 to > > Android, > > so I used the typical flags for building i965. > > --disable-gallium > > --disable-glu > > --disable-glw > > --disable-glut > > --enable-32-bit > > --enable-egl > > --enable-gles2 > > --enable-gles1 > > --enable-texture-float > > --with-dri-drivers=i965 > > --with-gallium-drivers= > > > > Note: This is in preparation for porting i965 to Android. > > CC: Chia-I Wu <o...@lunarg.com>, > > CC: Chih-Wei Huang <cwhu...@android-x86.org> > > Signed-off-by: Chad Versace <c...@chad-versace.us> > > --- > > Android.mk | 66 > > ++++++++++++++++++++++++++++++++++++++++++++ > > android/mesa_local_vars.mk | 32 +++++++++++++++++++++ > > 2 files changed, 98 insertions(+), 0 deletions(-) > > create mode 100644 Android.mk > > create mode 100644 android/mesa_local_vars.mk > > There's quite a bit of new build infrastructure here. What would it > take to fit this into either the existing autoconf support or add a > targeted configs/android? Duplicating a pile of make targets and > adding another way to configure/build mesa seems like it might not be > the best way to go. What are the current constraints that make > building mesa on android difficult?
I agree. I'd prefer not have yet another build infrastructure in the mix, unless there's a very good reason. Jose _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev