[SDL] SDL program crashing...
pphaneuf at gmail.com
Tue Apr 21 16:39:44 PDT 2009
On Tue, Apr 21, 2009 at 7:32 PM, Mike Mike <miketop0 at gmail.com> wrote:
> yh, I do know what an object file is.
> What I'm not sure of,is the proper way of making my .obj file
> available for others.
> Do you mean, I should find someone with a commercial version and make
> my .obj available for them to statistically link for me?
Nope, all this means is that if you don't want to provide source *and*
want to provide a statically linked binary, you can provide the object
files you used to make your binary available to those you distributed
the binary to.
This has to be in a form where if they had only SDL and the normal
development tools for the platform of that binary, they could re-make
your binary with their own SDL instead of the one you used.
Dynamically linking does this more or less automatically (one can just
replace the libsdl.so or SDL.DLL on the system, and they've done it),
but when statically linking, you have to take extra steps to make that
One thing that's also commonly done is to selectively static link
things, instead of using the -static option to link everything
statically. For example, the libc on a system is generally stable (or
providing good backward compatibility), but you might want to link
your own version of libpng statically. You can do that by replacing
the -lfoo with /path/to/libfoo.a on the linker command line (although
you sometimes have to move it around, due to the way linkers look up
symbols). You can then use a dynamic SDL and comply with the license
More information about the SDL