From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: "David E. Meier" <dev@eth0.ch>
Cc: cygwin-licensing@cygwin.com
Subject: Re: The term _linking_ in the licence
Date: Thu, 16 Jun 2005 15:41:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.61.0506161129050.4978@slinky.cs.nyu.edu> (raw)
In-Reply-To: <14363.193.17.199.5.1118934774.squirrel@193.17.199.5>
On Thu, 16 Jun 2005, David E. Meier wrote:
> I am confused about the GPL licence. Both suggested sites for reading
> before posting to this list about licencing only mention 'linking' with
> other programs.
>
> I face the following siuation:
>
> 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. 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?
AIUI -- no. Linking usually involves the linked parts running in the same
memory space, while fork/exec (used by system()) loads the program in a
separate memory space. But IANAL, and you can always say YANALATEYHSMBSI.
There's also the GPL FAQ which contains an answer to this exact question,
IIRC.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
next prev parent reply other threads:[~2005-06-16 15:41 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 [this message]
2005-06-16 16:30 ` Dave Korn
2005-06-17 8:40 ` David E. Meier
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=Pine.GSO.4.61.0506161129050.4978@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin-licensing@cygwin.com \
--cc=dev@eth0.ch \
/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).