From: "David E. Meier" <dev@eth0.ch>
To: cygwin-licensing@cygwin.com
Subject: RE: The term _linking_ in the licence
Date: Fri, 17 Jun 2005 08:40:00 -0000 [thread overview]
Message-ID: <15488.193.17.199.5.1118991876.squirrel@193.17.199.5> (raw)
In-Reply-To: <SERRANOmmhI4o28VIfw0000004a@SERRANO.CAM.ARTIMI.COM>
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....
>
>
>
prev parent reply other threads:[~2005-06-17 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 15:23 David E. Meier
2005-06-16 15:41 ` Igor Pechtchanski
2005-06-16 16:30 ` Dave Korn
2005-06-17 8:40 ` David E. Meier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15488.193.17.199.5.1118991876.squirrel@193.17.199.5 \
--to=dev@eth0.ch \
--cc=cygwin-licensing@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).