hi developers,
i would like to help adding a modularized runtime-loaded subsystem mechanism
in the SDL-lib.
is there someone already working on such issues?
cu
Daniel Adler
i would like to help adding a modularized runtime-loaded subsystem
mechanism
in the SDL-lib.
is there someone already working on such issues?
I’m not sure if you mean what I think, but I’ve written a DLL
(PortableExecutable W32) loader that can load
binary code at runtime which works yet for both windows and linux 
Live long and prosper /,
- Zordan Ehrwald
yes, the base would be such a loader, but it has different design
implications on the whole library code how code is called internally.
the SDL base library holds just the loader, the abstract code layer and User
API but no subsystem-driver implementation. It is linked purely against the
dynamic linkage library and the c library.
Each subsystem port would implement an interface (a structure/table of
function-pointers) and would be compiled to a shared object/DLL.
The base library loads and resolves demanded subsystems (through the
os-specific dynamic linker) and looks for a specific symbol - the interface
implementation, so it can make initial function-calls to the subsystem.
e.g.:On Wednesday 17 October 2001 15:51, you wrote:
i would like to help adding a modularized runtime-loaded subsystem
mechanism
in the SDL-lib.
is there someone already working on such issues?I’m not sure if you mean what I think, but I’ve written a DLL
(PortableExecutable W32) loader that can load
binary code at runtime which works yet for both windows and linux
file video_interface.h:
struct video_interface {
void (create_surface)(int width, int height);
/ … */
};
file linux/x11.c:
void x11__create_surface(int width, int height) {
/* X11 port implementation */
}
/* EXPORT */ video_interface video_x11 = {
x11__create_surface
};
The goal would be a library that don’t need to hold all subsystems in one big
file. especially those which relate contrary to each other, like video/x11
and video/linux-fbcon.
As a second, the relocation-time would be targeted to what is really needed
by the application.
so long,
plex
yes, the base would be such a loader, but it has different design
implications on the whole library code how code is called internally.the SDL base library holds just the loader, the abstract code layer and User
API but no subsystem-driver implementation. It is linked purely against the
dynamic linkage library and the c library.
For an example of how this can really become a mess real fast, I suggest
you have a look at QuakeForge (http://quakeforge.net/) at the first
opportunity. At this point, there is no interdependency checking and in
order to figure out how to get anything working you have to sit there and
read the source code which is seldom easy to follow.
While it would be nice if SDL did things like try to dlopen libasound and
simply fail quietly to set up ALSA sound if it’s not there, I think that
trying to break all of the things that are part of SDL into little
libraries will only lead to the same decline in usability as found in QF
today. Given the fact that is one of the reasons I use SDL is so that I
may never again have to deal with that kind of convoluted crap, I’m a bit
opposed to risking the same thing in SDL.
Each subsystem port would implement an interface (a structure/table of
function-pointers) and would be compiled to a shared object/DLL.The base library loads and resolves demanded subsystems (through the
os-specific dynamic linker) and looks for a specific symbol - the interface
implementation, so it can make initial function-calls to the subsystem.
We do this for OpenGL. You would not BELIEVE some of the problems that
have shown up. We fixed them because they were ultimately simple fixes
even if finding them was very complex and it was worth it to be able to
swap OpenGL libs around like that.On Wed, Oct 17, 2001 at 09:46:27PM +0000, plex wrote:
–
Joseph Carter Free software developer
Would it be acceptable to debian policy if we inserted a crontab
by default into potato that emailed bill.gates at microsoft.com
every morning with an email that read, “Don’t worry, linux is a
fad…”
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20011017/178c8670/attachment.pgp