I have been implementing a port (unofficial) of SDL for Epoc ER6 (Crystal).
Currently, part of the SDL demos work in Epoc. Hopefully, I could make some
kind of release during next couple of months.
One problem in this port is that Epoc do not allow static/global variables
in DLL libraries. So I could only use static linking with SDL. This might
cause(?) some problems with LGPL.
Regards,
Hannu Viitala
@Hannu_Viitala
I have been implementing a port (unofficial) of SDL for Epoc ER6 (Crystal).
Currently, part of the SDL demos work in Epoc. Hopefully, I could make some
kind of release during next couple of months.
Very cool. 
One problem in this port is that Epoc do not allow static/global variables
in DLL libraries. So I could only use static linking with SDL. This might
cause(?) some problems with LGPL.
It might. We’ll keep that in mind for SDL 1.3, and we’ll try not to use
any globals.
See ya,
-Sam Lantinga, Lead Programmer, Loki Software, Inc.
One problem in this port is that Epoc do not allow static/global variables
in DLL libraries. So I could only use static linking with SDL. This might
cause(?) some problems with LGPL.It might. We’ll keep that in mind for SDL 1.3, and we’ll try not to use
any globals.
That would be great. In Epoc, the loader do not support static data blocks in
dll-modules. If absolutely needed, using Tread Local Storage (like in MsWindows),
global data can be implemented. However, that makes it platform specific and has
some performance penalty.
—> Hannu