From: Brian P. <bri...@tu...> - 2004-10-15 14:45:32
|
James Amendolagine wrote: > On Tue, 2004-10-12 at 11:16, James Amendolagine wrote: > >>On Tue, 2004-10-12 at 09:03, James Amendolagine wrote: >> >>>On Tue, 2004-10-12 at 08:26, Brian Paul wrote: >> >>>>What kind of Chromium configuration did you test with? >>>> >>> >>>The first one was a client renderer. I'm currently going through and >>>testing some client - server configurations. >>> >> >>OK, I think that I see what you may have been getting at. >> >>The client-server tests failed with a link error. >>So append these files to the list of modified Chromium files: >> >>packer/pack_swap_texture.c >>packer/pack_texture.c >> > > > I've run through a simple sanity test of each of ES the calls in a > client-server mode, and everything seems to work now. > > A few more files needed to be adjusted: > > include/state/cr_statetypes.h > packer/pack_currenttypes.py > packer/pack_lights.c > packer/pack_materials.c > packer/pack_matrices.c > packer/pack_swap_texture.c > packer/pack_texture.c > packer/packer.py > packer/packer_special > spu/tilesort/length_table.py > spu/tilesort/pinch_convert.py > state_tracker/convert.py > state_tracker/state_current.py > state_tracker/state_lighting.c > > > I've briefly looked through the license, and I'm not sure what the exact > restrictions on chromium are (as far as it's open-source nature). It's > not GPL as far as I can tell. > > I wasn't too worried up front, as I intend to share the source. Still, I > would like to know, what are the restrictions of the license? They > appear to be fairly loose, and not require sharing of the source. It's a standard BSD license. See http://www.opensource.org/licenses/bsd-license.php -Brian |