Dan Stefan Rundberget wrote:
If you dynamicly link with gtk+ (LGPL) you are forced to give the users permission to 
modify the binaries AND reverse engineer them for personal use, the LCL-LGPL doesn't. 
This means that even if you staticly link LGPL libraries (like gtk+), you still can't use 
licenses like X11 (which I prefere). Because the license has to "inherit" this 
restriction and pass it on to any derived works. And it becomes pointless to use the X11 
license, since you have to add this restrctions to people who want to make 
(properitary/closed source) derived works.  And I don't want this restriction on my own 
code. This is the reason I'm avoiding the use of LGPL libraries. So If their isn't any 
way around this I can't use lazaru, and I want to make my apps cross platform and with a 
GUI!

But what can a user of your software do with reverse engineer??? He can at best get a lot of meaningless assembler stuff without the source. Perhaps more if he knows the compiler and has a deassembler for it.

I think this was created to allow people to reverse engeneer drivers that use glibc and things like that ... but I can´t be sure.

And BTW, in the modification it says:
"link this library with independent modules to produce an executable (...) and to 
copy and distribute the resulting executable under terms of your choice"

What about third party libraries, which isn't am executable, (or am I wrong? I appologize if I am.)

I think that Libraries are also considered executables. Under windows a dll is just a slightly different .exe file (1 bit marks it as DLL). It has the begin ... end. section and all other stuff from a exe. Can anyone clear this point?

I also beliave that Lazarus licence was created with the explicit purpouse of allowing people to develop Closed Source and Paid software using Lazarus and Free Pascal.

That minor problem you encountered is with GTK, not Lazarus. It won´t exist under Lazarus + Windows for example. The only other option is to use Qt, but it is even more restrictive unless you pay for Qt. By the way, the Lazarus interface for Qt is incomplete at the moment.

Also take notice that Lazarus is even more free of the problem you encountered with LGPL then most other languages. If you write code in c or c++ you need to link to glibc, witch is LGPL. You can get rid of this problem by finishing the Qt interface =)

Felipe

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to