From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Visual Studio linking
Date: Mon, 07 Jun 2004 16:25:00 -0000 [thread overview]
Message-ID: <20040607162514.GB4767@coe.casa.cgf.cx> (raw)
In-Reply-To: <Mahogany-0.66.0-604-20040607-171325.00@bakbone.co.uk>
On Mon, Jun 07, 2004 at 05:13:25PM +0100, Alastair Growcott wrote:
>>A .def file is generated for cygwin when the DLL is built, actually.
>
>I'm not building the Cygwin dll, so I need this step.
>
>>5a) Modify the license of your program to the GNU General Public
>>License, since your binary has now become GPLed, meaning that you must
>>now offer the source code to your sources under the terms of the GPL.
>
>My program is non-distributable. I am using it to run unit tests
>internally.
>
>I thought that, under the terms of the GPL, if my binary links
>dynamically to the Cygwin DLL, I do NOT have to offer my source code
>up, I only need to ensure that people can use my software against
>future (or past) versions of Cygwin by rebuilding the DLL themselves.
>This includes either distributing the Cygwin DLL source code or
>ditributing a link to somewhere they can obtain it.
>>5) Download crt0.c from the cygwin website and include it in your
>>sources. Modify it to call my_crt0() instead of cygwin_crt0().
You're including crt0.c in your source code. That's not linking
dynamically. You are also using a .def file for your linking rather
than calling LoadLibrary and cousins.
AFAICT, you aren't doing anything differently from what a normal build
of a binary using gcc and would do.
>Or is that the lesser GPL?
>
>Surely the source code will not be GPL'ed if I do not make it or the
>binary publically available!
I suspect that you probably haven't read the GPL FAQ. This section
is probably pertinent:
http://www.gnu.org/licenses/gpl-faq.html#TOCGPLRequireSourcePostedPublic
but the rest should make interesting reading as well.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-06-07 16:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 8:20 Alastair Growcott
2004-06-02 8:52 ` Max Bowsher
2004-06-02 9:18 ` Re[2]: " Alastair Growcott
2004-06-02 12:16 ` Re[3]: " Alastair Growcott
2004-06-02 13:45 ` Re[4]: " Alastair Growcott
2004-06-02 13:55 ` Dave Korn
2004-06-07 14:40 ` Re[5]: " Alastair Growcott
2004-06-07 14:56 ` Christopher Faylor
2004-06-07 16:15 ` Re[2]: " Alastair Growcott
2004-06-07 16:25 ` Christopher Faylor [this message]
2004-06-08 9:04 ` Alastair Growcott
2004-06-08 13:02 ` Christopher Faylor
2004-06-07 20:42 ` Re[5]: " Joshua Daniel Franklin
2004-12-12 22:38 Daniel Starin
2004-12-12 22:55 ` Larry Hall
2004-12-17 21:35 ` Daniel Starin
2004-12-17 22:20 ` Larry Hall
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=20040607162514.GB4767@coe.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin@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).