Re: LGPL
- From: "Sergio A. Kessler" <ser perio unlp edu ar>
- To: gnome-devel-list gnome org, sopwith redhat com
- Subject: Re: LGPL
- Date: Sat, 10 Apr 1999 05:58:03 -0300
Elliot Lee <sopwith@redhat.com> el día Sun, 11 Apr 1999 20:21:23 -0400
(EDT), escribió:
>On Sat, 10 Apr 1999, Sergio wrote:
>
>> yes, in the Delphi world we deal with components (a library of object
>> and routines) that are linked statically in the exe, thus forming a
>> single executable that run in any basic environment, if you want to
>> dinamically link the library you could (in recent versions of Delphi),
>> but it is a mess, because you'll have to deploy the _whole_ library
>> (big) along with the exe and complicate the life of the final user.
>>
>> If you link statically only the objects that are used go in
>> the exe (a kind of runtime specialized for your program).
>>
>> And in Megido (our Delphi for Gnome) we have a _lot_ of this
>> kind of code under the LGPL and now we found this problem.
>
>Requiring a libmegido.so.1 to run apps created using Megido would be no
>different than requiring a libgnome.so.1 to run GNOME apps.
with the current code we have, we can't do that, even if it is
possible we don't want this very much and in a perfect environment
we want to let the programmer decide how to package _their_ app
using our libraries statically or dinamically linked without
problems.
>Alternatively you could create the shared library on a per-application
>basis, e.g. libmyapp_lgpl.so.0.
this will create a nigthmare for deployment and we are forcing
the developer to do things he don't want to do (ie. their freedom
go away)
Sergio
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]