This is the mail archive of the cygwin-licensing@cygwin.com mailing list for the cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: The term _linking_ in the licence


Hi Dave and Igor,

thanks for answering my question. That cleared it up.

Dave

>> I have written a program in C# that makes use of tools like ssh, rsync
>> and
>> some bash shell built-ins. The C# program is the main .exe and does not
>> link to any of the GPL-programs while building and therefore the C#
>> binary does not contain any cygwin code.
>
>   Bear in mind there's also such a thing as runtime linking... If you
> LoadLibrary ("cygwin1.dll") and GetProcAddress a function and call it,
> that counts as linking and your app must be GPL'd.
>
>>The GPL-exe's are called as system calls at runtime via the cmd.exe.
>>
>> Does the C# program need to be redistributed under the GPL as well?
>
>   However, as Igor said, as long as the executables and process spaces are
> completely separate, you will have no problem.  The GPL spreads out within
> a single process space, but it is not conveyed across IPC mechanisms!
>
>   And also, bear in mind that if you're distributing the ssh/rsync/bash
> binaries along with your app, you need to provide (or offer to provide)
> the sources for them.
>
>     cheers,
>       DaveK
> --
> Can't think of a witty .sigline today....
>
>
>



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]