On 04 Jul 2008, at 17:15, Vladimir Zhirov wrote:
Suppose application and library files are:
project1.pas
project1.o
project1.compiled
lgpled_lib.pas
lgpled_lib.o
lgpled_lib.ppu
What files I must make public, and how people are supposed to use them
in order to relink my application with newer/
Tomas Hajny wrote:
> I believe that one of the ways would be compiling lgpled_lib.pas into a
> shared library/DLL and having it linked to your program dynamically,
> another solution would be providing interested users with all the required
> object files (*.o), libraries (.a) and a linker script.
On Fri, Jul 4, 2008 at 1:15 PM, Vladimir Zhirov <[EMAIL PROTECTED]> wrote:
> Would you please help me to find out the steps I should follow
> to comply with LGPL if my application is built using FPC
> and uses pascal source code of LGPL'ed library?
Which library are you using that is LGPL?
--
Fe
On Fri, July 4, 2008 18:15, Vladimir Zhirov wrote:
Hi,
> Would you please help me to find out the steps I should follow
> to comply with LGPL if my application is built using FPC
> and uses pascal source code of LGPL'ed library?
>
> Section 4 of LGPL requires to
>
>> d) Do one of the following:
Hi,
Would you please help me to find out the steps I should follow
to comply with LGPL if my application is built using FPC
and uses pascal source code of LGPL'ed library?
Section 4 of LGPL requires to
> d) Do one of the following:
> 0) Convey the Minimal Corresponding Source under the terms of
