> > SDL 1.2 is still in the SRPMS for the OLPC project on the fedora server, but AFAIK it is not being used > when the actual OS Image is being created. > > SDL in itself is not that big, but did you also want auxiliary libraries pulled in also? For example, > SDL-image, SDL-sound, SDL-ttf, etc, etc. > > Darryl
SDL-image would be pretty much be required as otherwise the default image format would be bitmaps. Not very space efficient. SDL-ttf would be nice, as long as freetype is already part of the base system? SDL-sound would be nice, unless some other simple API is available? Those three would be enough to include with the base system. Any other needed libs could be included with the app in question. The reason for wanting SDL in there is that it's a clean, clear cross-platform API for low level access. It makes the life of a programmer who's only interested in programming at that that level much easier. Not everyone likes dealing with windowing system APIs. And easier = more apps :D Not to mention the existing quantity if SDL apps out there. If SDL could be confirmed as part of the base system then people (like me :) can start building their style of app right now with a high level of confidence that there would be minimal changes to get it working on the laptop. With that assurance I could start right now without even having to care what the ultimate desktop would be like and what APIs were (dis)approved. ttfn, John PS Surely SDL Duke3D is enough of an argument :P -- olpc-software mailing list [email protected] https://www.redhat.com/mailman/listinfo/olpc-software
