On Tue, Jan 05, 2010 at 08:58:54AM -0700, Brian Paul wrote: > Chia-I Wu wrote: > >Hi Brian, > > > >The attached patches are trivial fixes to a distribution problem and > >cofigure.ac. I've done a clean build test > > > >$ make tarballs > >$ tar xf MesaLib-7.7-devel.tar.gz > >$ cd Mesa-7.7-devel/ > >$ ./configure --with-state-trackers=egl,es > >$ make -j4 CC="ccache gcc" > It's not building for me. > [...] > gmake[4]: Entering directory > `/home/projects/Mesa-head/mesa/src/gallium/state_trackers/egl' > gmake[4]: Nothing to be done for `default'. > gmake[4]: Leaving directory > `/home/projects/Mesa-head/mesa/src/gallium/state_trackers/egl' > gmake[4]: Entering directory > `/home/projects/Mesa-head/mesa/src/gallium/state_trackers/es' > gmake[4]: *** No rule to make target > `../../../../src/mesa/es/libes1gallium.a', needed by > `../../../../lib/libGLESv1_CM.so'. Stop. > gmake[4]: Leaving directory > `/home/projects/Mesa-head/mesa/src/gallium/state_trackers/es' > gmake[3]: *** [subdirs] Error 1 Have you regenerate configure script after the last patch to configure.ac? When configured with --with-state-trackers=egl,es, the SRC_DIRS should read like
SRC_DIRS = mesa/es glx/x11 mesa glew egl glu glw glut/glx gallium gallium/winsys mesa/es should be built before gallium. > I'm a bit confused about the organization of the code. There's ES > code both in src/mesa/es and src/gallium/state_trackers/es/. I > don't have time right now to dig through all this and figure it out. > I think it would be really helpful to have a docs/es.html file that > explained everything. src/mesa/es/ builds libes1gallium.a and libes2gallium.a. They serve the same purpose as libmesagallium.a does for OpenGL. There is almost nothing in src/gallium/state_trackers/es/. It mainly provides rules to link various libraries to produce the final libGLES*.so. I will be off for some days. I will write up the documentation after I come back. > >and tested all ES1/ES2 demos. > >Do you have anything you want me to change/fix in this branch? If it all > >seems > >ok and the timing is fine to you, I would like to start fixing conflicts and > >merge it to master. > As mentioned above, it would be good to have some docs to explain > all the pieces. > >I pinged the fdo admin again (bug #23272) some time ago, but I still did not > >get any response. Could you help me merge master to this branch? I want to > >fix any issue results from the merge in this branch, and when I am done, I > >will > >ping you back so that it can be merged to master. If you have better ideas, > >please let me know. Thanks. > I'll ping the fd.o admin too. I'd prefer that you do all the merge work. Thanks. That would be even better. -- Regards, olv ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
