Mercurial > sdl-ios-xcode
view src/video/Xext/README @ 956:4263beff9e38
Date: Mon, 30 Aug 2004 18:20:25 +0200
From: Joost Baas
Subject: why call arts artsc?
I, and a few other people at the mplayer-docs-mailinglist were wondering why
you decided to call arts artsc. I understand usually users have nothing to do
with libsdl, just developers, but because you can choose the audio-driver
being used by mplayer, one of which is sdl, and you can also choose the sdl
subdriver, it is necessary to have a well-known or logical name. artsc is not
the logical choice, and it's very hard to look up the right name if you don't
know what you're looking for.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Fri, 17 Sep 2004 13:25:06 +0000 |
parents | b87d8d4c205d |
children |
line wrap: on
line source
The reason these libraries are built outside of the standard XFree86 tree is so that they can be linked as shared object code directly into SDL without causing any symbol collisions with code in the application. You can't link static library code into shared libraries on non-x86 Linux platforms. Since these libraries haven't become standard yet, we'll just include them directly. These sources are synchronized with XFree86 4.2.1