with modular X now quite usuable, we’d like to keep libsdl in Gentoo from
using any of the bundled X code (src/video/Xext/*) at all and pull from the
installed X system libraries
i imagine this isnt a trivial thing to do, so rather than just complaining and
waiting for someone else to do it, can someone post some hints on how to go
about doing this properly ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20060526/8c185e45/attachment.pgp
with modular X now quite usuable, we’d like to keep libsdl in Gentoo from
using any of the bundled X code (src/video/Xext/*) at all and pull from the
installed X system libraries
Any particular reason?
i imagine this isnt a trivial thing to do, so rather than just complaining and
waiting for someone else to do it, can someone post some hints on how to go
about doing this properly ?
It’s probably just a matter of changing the #include statements that
refer to those files, adding a bunch of dynamic X11 syms, and then changing
the configure script to include the right libraries and exclude the built-in
sources.
See ya,
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment
i imagine this isnt a trivial thing to do, so rather than just complaining and
waiting for someone else to do it, can someone post some hints on how to go
about doing this properly ?
I would say “don’t” unless there’s a reason I can’t see. They don’t add
that much overhead, it only needs to talk to basic Xlib in most cases
as-is, and it would be a pain to seperate it out until we were going to
just jettison the code from SDL altogether.
–ryan.
less things to maintain/track/worry about is what it really comes down to
plus, http://bugzilla.libsdl.org/show_bug.cgi?id=242 seems like a good
reason 
-mike
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20060620/d8840bac/attachment.pgpOn Friday 26 May 2006 13:47, Sam Lantinga wrote:
with modular X now quite usuable, we’d like to keep libsdl in Gentoo from
using any of the bundled X code (src/video/Xext/*) at all and pull from
the installed X system libraries
Any particular reason?
Hello !
with modular X now quite usuable, we’d like to keep libsdl in Gentoo
from using any of the bundled X code (src/video/Xext/*) at all and
pull from the installed X system libraries
As i am not into X, what would
this mean for SDL and developers ?
What means modular X here ?
CU
As i am not into X, what would
this mean for SDL and developers ?
What means modular X here ?
Modular X means that X11 is splitted on hundreds of small packages -
different libraries, drivers and protocols are now different packages
in X 7.0 (that is the only difference from 6.9). This allows to update
parts of X independtly, and not to install all drivers, libs and
protocols, that are not needed on particular system.
All X 7.x branch will be modular, so it would be better if SDL make
use of this modularity now. IMHO it is generally better idea to use
system libraries than bundled, as this helps to avoid conflicts.
All X 7.x branch will be modular, so it would be better if SDL make
use of this modularity now. IMHO it is generally better idea to use
system libraries than bundled, as this helps to avoid conflicts.
There are a lot of systems that don’t use x.org at all, or use pre-7.0
builds, so we’re going to have to consider a non-modular X11 for a long
long time yet.
This doesn’t generally affect SDL, though…it’s all the same X11
libraries once they get onto a system.
–ryan.
This doesn’t generally affect SDL, though…it’s all the same X11
libraries once they get onto a system.
Of course.
What reasons are for keeping some X libraries bundled with SDL?
What reasons are for keeping some X libraries bundled with SDL?
Not being able to guarantee they exist on the end user’s system, mostly.
libXME, for example, is almost never available, since it only ships with
the Xi Grahphics X servers and not Xfree86/x.org, but is needed on the
Xi servers to change video modes. Bundling the tiny bit of code in SDL
made a lot of sense, since it helps SDL libraries run everywhere in
binary-only packages. Other bundled XFree extensions were added when
they were really new, and weren’t necessarily on a developer’s machine,
either. This has become less of a problem as time went on.
Some of this could probably move to the dynamic loader mechanism and be
removed from SDL’s source tree, if the dynamic X11 code gets a few
improvements, and just disabled on platforms that don’t have the library.
–ryan.