-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joakim Sindholt wrote: > I've heard a little talk here and there and glisse pointed out I should > take it to the ML. > > The basic idea is that instead of binding 1 winsys, 1 state tracker and > a couple of pipes into every single library we churn out, we define some > sort of API between winsys and state_tracker so that we can split the > library into 1 x (winsys + n pipes) and compile state trackers > separately and just load our "Gallium3D library" at runtime. > The way I see it we have a couple of options:
This idea has been rejected for Mesa in the past. Any time you add an exposed API, you add binary compatibility requirements. That brings only pain. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr4p9MACgkQX1gOwKyEAw+fxQCbBuhhxkZ39e4vBeu87kCYyWXu VDwAnjFmuBVuG3gTvXctOiZ+gS7PCQTR =ZTsd -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
