the attached patch gets the SDL library and examples running on win32.
please test on existing platforms by applying and running
.\parrot examples\sdl\blue_rect.imc
additionally, you may test against the minesweeper and tetris examples.
these examples start on win32, but are buggy.
~jerry
> the attached patch gets the SDL library and examples running on win32.
> please test on existing platforms by applying and running
> .\parrot examples\sdl\blue_rect.imc
I don't see a patch in this mail or in RT. Can you re-send?
-- c
>> > the attached patch gets the SDL library and examples running on win32.
Are there more Win32 libs that have the same naming conventions:
unixish: win32:
libSDL SDL
The question is, if the dynext loader should try to strip "^lib" off the
library name.
leo
the convention on windows is not to include the "lib" prefix, however there
are exceptions. notably, the windows svn client, and trillian, my irc
client. centralizing the logic of loading libraries so it Just Works on any
platform makes sense to me. this should follow for other conventions on
other platforms, as well. i dunno what macOS and os2 do.
and then i could stop patching runtime libraries and move on to something
more exciting :)
> leo
~jerry
>>The question is, if the dynext loader should try to strip "^lib" off the
>>library name.
>
> the convention on windows is not to include the "lib" prefix, however there
> are exceptions.
Ok, let's try it. Please test rev 7813.
leo
works! the win32-specific stuff can be ripped out of
runtime/library/pcre.imc && SDL.imc.
or i'll submit a patch if you'd rather.
leo
~jerry
> works! the win32-specific stuff can be ripped out of
> runtime/library/pcre.imc && SDL.imc.
> or i'll submit a patch if you'd rather.
There shouldn't be any Win32-specific stuff in SDL.imc now. (I don't
see any.)
There's Debian-specific stuff, but that's just Debian being charmingly
itself.
If Jerry's happy, I'm happy and the RT overlords can close this ticket.
-- c
On 12 Apr 2005 18:10:49 -0000, chromatic via RT <
> There's Debian-specific stuff, but that's just Debian being charmingly
> itself.
That should go away too. The canonical fix is to create the missing
symlinks and probably submit patches to debian.
leo