Quoting Jens Owen ([EMAIL PROTECTED]): > Brian Paul wrote: > >Where do you propose that the files currently in Mesa/src/dri/ (such as > >dri_glx.c, glxclient.h, etc) belong? src/dri-es/ is the place I was > >planning on. > > > >I'm trying to keep the tree fairly shallow (one of the things that > >intimidates people about the XFree86/DRI tree is its size and depth) so > >I'm not sure we need drivers/dri/ yet. > > > >Also, I want to try to keep all source files as leaves in the tree. That > >is, a directory foo/ won't contain both files and subdirs; just one or > >the other. > > Brian, > > One thing that would help me understand how this new tree structure (and > how having the Mesa DRI driver in the tree) will work would be to > understand where the resulting binary files would end up *after* a > build. Specifically, can a radeon DRI driver module be built from this > standalone tree? Where will it reside? Where will an embedded Mesa > radeon driver module reside? and finally, future window system > bindings, for example a DirectFB Mesa driver module. Where would that live?
There will be no DirectFB Mesa driver module. The DirectFB specific part resides in the loadable module of IDirectFBGL. This module will use the DRI driver interface from drivers/dri/, i.e. DRIMesaCreateContext etc. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
