Hello I have some confusion on conforming to the LGPL licence of SDL and
what is required.
If I wanted to release a non open source application and did not want to
share the object files so that a user could recompile using a later version
of SDL what is required on my behalf? Is it true that by just linking to the
library is enough as it dynamically links in the dll/so object or is it
required that I include the headers in my application and manually load in
the dynamic library and the addresses of the functions?
Thanks.
Hello I have some confusion on conforming to the LGPL licence of SDL and
what is required.
If I wanted to release a non open source application and did not want to
share the object files so that a user could recompile using a later version
of SDL what is required on my behalf? Is it true that by just linking to the
library is enough as it dynamically links in the dll/so object or is it
required that I include the headers in my application and manually load in
the dynamic library and the addresses of the functions?
Thanks.
“This doesn’t mean that you need to distribute what are typically known
as “object files.” It only means that you need to distribute a
dynamically linked binary.”
I am sorry If I do not understand you correctly but the question is how do I
"dynamically link" sdl
"Is it true that by just linking to the library is enough as it dynamically
links in the dll/so object or is it required that I include the headers in
my application and manually load in the dynamic library and the addresses of
the functions?"On Wed, Dec 3, 2008 at 4:50 PM, Donny Viszneki <donny.viszneki at gmail.com>wrote:
Users must be able to link your application to any conforming SDL dylib.
This doesn’t mean that you need to distribute what are typically known
as “object files.” It only means that you need to distribute a
dynamically linked binary.A point of contention I notice many people struggle with, in case you
were wondering: it is perfectly alright to distribute a statically
linked copy of your program as long as you always make a dynamically
linked copy available with it. The easiest way IMHO to do this is to
include both in your downloads (that is of course second to the ease
with which you can simply release the source code of your project,
which has many benefits aside from merely complying with the LGPL.)It should also be noted that if you modify your SDL in any way, those
changes cannot be withheld from anyone who gets their hands on a copy
of your modified SDL binaries. SDL is OPEN SOURCE even if your
applications are not.On Wed, Dec 3, 2008 at 8:24 AM, tome toyou <@tome_toyou> wrote:
Hello I have some confusion on conforming to the LGPL licence of SDL and
what is required.
If I wanted to release a non open source application and did not want to
share the object files so that a user could recompile using a later
version
of SDL what is required on my behalf? Is it true that by just linking to
the
library is enough as it dynamically links in the dll/so object or is it
required that I include the headers in my application and manually load
in
the dynamic library and the addresses of the functions?
Thanks.
Sdl mailing list
Sdl at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
I am sorry If I do not understand you correctly but the question is how
do I
"dynamically link" sdlIf your application won’t run without SDL.dll, it is dynamically
linked to SDL.dll.
So I have to remove it from the development environment paths and also if it
is in any path which windows would look for to see if I am dynamically
linking it? I thinking I will just link to it any way I want and say "Sam
come and find me I you want to sue me"
Thanks for nothing.On Wed, Dec 3, 2008 at 7:16 PM, Donny Viszneki <donny.viszneki at gmail.com>wrote:
On Wed, Dec 3, 2008 at 12:25 PM, tome toyou <@tome_toyou> wrote:
Since you seem to be using Windows, I recommend trying this software out:
http://www.dependencywalker.com/On Wed, Dec 3, 2008 at 2:43 PM, tome toyou wrote:
On Wed, Dec 3, 2008 at 7:16 PM, Donny Viszneki <@Donny_Viszneki> wrote:
If your application won’t run without SDL.dll, it is dynamically
linked to SDL.dll.So I have to remove it from the development environment paths and also if it
is in any path which windows would look for to see if I am dynamically
linking it? I thinking I will just link to it any way I want and say "Sam
come and find me I you want to sue me"
Thanks for nothing.
If your application won’t run without SDL.dll, it is dynamically
linked to SDL.dll.So I have to remove it from the development environment paths and also
if itis in any path which windows would look for to see if I am dynamically
linking it? I thinking I will just link to it any way I want and say
"Samcome and find me I you want to sue me"
Thanks for nothing.Since you seem to be using Windows, I recommend trying this software out:
If you’re using GNU tools, you should be able to use ldd.
"Is it true that by just linking to the library is enough as it dynamically
links in the dll/so object…"
So it turns out that just linking to SDL.lib and SDLmain.lib is all that is
required as it loads the dynamic library in itselfOn Wed, Dec 3, 2008 at 8:04 PM, Donny Viszneki <donny.viszneki at gmail.com>wrote:
On Wed, Dec 3, 2008 at 3:01 PM, Donny Viszneki <donny.viszneki at gmail.com> wrote:
On Wed, Dec 3, 2008 at 2:43 PM, tome toyou <@tome_toyou> wrote:
On Wed, Dec 3, 2008 at 7:16 PM, Donny Viszneki < donny.viszneki at gmail.com> wrote: