On Tue, Dec 29, 2009 at 9:58 AM, tom fogal <tfo...@alumni.unh.edu> wrote: > Brian Paul <bri...@vmware.com> writes: >> tom fogal wrote: >> > I'd like to trim down the libGL ABI. Appended is the start of an >> > approach that is going to work, and I just need to put in the time >> > to complete everything. >> > >> > Thoughts? >> >> This looks pretty good. Just a few comments. >> >> 1. The other glapi generator scripts are written in Python. It would >> be nice if we'd keep with that convention, rather than use sh. > > Okay. > >> 2. We'll need a way to add extra symbols to the export map in some >> cases. For example, the libOSMesa.so library needs to access some >> symbols in libGL.so, such as swrast_CreateContext(), etc. This could >> be as simple as supporting an additional exports file that gets >> appended onto the gl_exports file. > > It would be nice for me/my projects if libOSMesa.so was completely > standalone. Can we just include all of those needed symbols while > building it? > > Of course, you're probably referencing one example among many, and such > a feature is simple, so I'll include it regardless.
You could also have mklib support multiple exports files and do the concatenation there. Then you could have gl.exports.osmesa and only include it when you were doing OSMesa on GL. -- Dan ------------------------------------------------------------------------------ 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
