Striping DLL?

There are some strange thing with striping the DLLs cross-compiled
for Win32. I use mingw32 and cross compile SDL, SDL_mixer, SDL_image,
SDL_ttf, smpeg, jpeg win32 DLLs under Linux. But after I use

/usr/local/cross-tools/bin/i386-mingw32msvc-strip 

On some of the DLLs, runtime error will occur at loading them. I
can strip the SDL.DLL fine, but not on other DLLs, can somebody
point out what I did wrong? I though “strip” is used to remove those
debugging info from binaries?

Regards,
.paul.

There are some strange thing with striping the DLLs cross-compiled
for Win32. I use mingw32 and cross compile SDL, SDL_mixer, SDL_image,
SDL_ttf, smpeg, jpeg win32 DLLs under Linux. But after I use

/usr/local/cross-tools/bin/i386-mingw32msvc-strip

On some of the DLLs, runtime error will occur at loading them. I
can strip the SDL.DLL fine, but not on other DLLs, can somebody
point out what I did wrong? I though “strip” is used to remove those
debugging info from binaries?

Don’t strip them. If you strip the DLL’s, they won’t work on some
versions of Windows. Are you building custom versions of the libraries?
If not, you should just be able to use the precompiled binaries from
the website…

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment

My intention was that stripped binaries are always smaller
in size.

Thanks for the clarification!

Regards,
.paul.On Mon, Mar 25, 2002 at 11:15:40PM -0800, Sam Lantinga wrote:

There are some strange thing with striping the DLLs cross-compiled
for Win32. I use mingw32 and cross compile SDL, SDL_mixer, SDL_image,
SDL_ttf, smpeg, jpeg win32 DLLs under Linux. But after I use

/usr/local/cross-tools/bin/i386-mingw32msvc-strip 

On some of the DLLs, runtime error will occur at loading them. I
can strip the SDL.DLL fine, but not on other DLLs, can somebody
point out what I did wrong? I though “strip” is used to remove those
debugging info from binaries?

Don’t strip them. If you strip the DLL’s, they won’t work on some
versions of Windows. Are you building custom versions of the libraries?
If not, you should just be able to use the precompiled binaries from
the website…

-----Oorspronkelijk bericht-----
Van: paul [mailto:paul at theV.net]
Verzonden: dinsdag 26 maart 2002 8:39
Aan: sdl
Onderwerp: Re: [SDL] striping DLL?

There are some strange thing with striping the DLLs cross-compiled
for Win32. I use mingw32 and cross compile SDL,
SDL_mixer, SDL_image,

SDL_ttf, smpeg, jpeg win32 DLLs under Linux. But after I use

/usr/local/cross-tools/bin/i386-mingw32msvc-strip 

On some of the DLLs, runtime error will occur at loading them. I
can strip the SDL.DLL fine, but not on other DLLs, can somebody
point out what I did wrong? I though “strip” is used to
remove those

debugging info from binaries?

Don’t strip them. If you strip the DLL’s, they won’t work on some
versions of Windows. Are you building custom versions of
the libraries?
If not, you should just be able to use the precompiled binaries from
the website…

My intention was that stripped binaries are always smaller
in size.

They can indeed become smaller but as Sam allready mentioned, with some
Win9x versions the .DLL may produce side effects. Use upx for
compressing
the .DLL files, it works for WIN32 .EXE’s to!. You can grab a version at

http://upx.sourceforge.net.

At the moment I haven’t had complaints using this method. Only debugging
is a pain in the butt with those files :confused:

Thanks for the clarification!

Regards,
.paul.

Regards,

Niels Wagenaar> On Mon, Mar 25, 2002 at 11:15:40PM -0800, Sam Lantinga wrote:

My intention was that stripped binaries are always smaller
in size.

Thanks for the clarification!

Regards,
.paul.

You might want to try UPX (an executable compressor) if you like small
executable sizes (without noticable overhead). Works also on DLLs. I don’t
have the link here, do a search on google.> -----Original Message-----

From: paul at theV.net [mailto:paul at theV.net]

Dominique Biesmans

My intention was that stripped binaries are always smaller
in size.

Thanks for the clarification!

Regards,
.paul.

You might want to try UPX (an executable compressor) if you like small
executable sizes (without noticable overhead). Works also on DLLs. I don’t
have the link here, do a search on google.

If you’re looking to compress Win32 EXE files, I recommend NeoLite. It’s not
free, but I’ve used it in a couple of commercial products and have never had
a problem that was related to the compression. It compresses EXE’s and
DLL’s, and you can specify what parts to compress (code, resources, etc)

http://www.neoworx.com/products/neolite/> From: sdl-admin at libsdl.org [mailto:sdl-admin at libsdl.org]On Behalf Of

Sent: Tuesday, March 26, 2002 2:01 AM
To: 'sdl at libsdl.org
Subject: RE: [SDL] striping DLL?

-----Original Message-----
From: paul at theV.net [mailto:paul at theV.net]


John Hattan Sweet software for a saturnine world
@John_Hattan http://www.thecodezone.com

You can also build without the -g option, which will result in smaller,
but not completely stripped binaries. Don’t build with the -s option,
which essentially does a strip of the objects.

You might also try strip -g … I don’t know if that’s less intrusive.

See ya!
-Sam Lantinga, Software Engineer, Blizzard Entertainment