Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<42B9A393.94491BD3@dessent.net>
Date:	Wed, 22 Jun 2005 10:44:51 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [FAQ Alert, ping JDF!] RE: How to make DLLs in cygwin for MSVC and BCB
References:	<42B9854D DOT DBC0BD AT dessent DOT net> <SERRANO8xtp1nRZRHOR00000150 AT SERRANO DOT CAM DOT ARTIMI DOT COM> <d9c2st$r4g$1 AT sea DOT gmane DOT org>
X-Spam-Report:	-5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Patrick Rotsaert wrote:

> No problem that my dll will fall under the GPL.
> Just out of curiosity, does this also apply for applications that use my
> DLL?

As far as I understand it, "linking" as defined by the GPL is when you
incorporate code into the running process space.  If you keep them
seperated into different processes (e.g. one program spawns/execs
another) that is not considered linking.  So dynamic linking = yes,
spawning a seperate process and communicating via IPC = no.  But then
again <http://cygwin.com/acronyms/#YANALATEYHSMBSI>.

Brian

--
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/

- Raw text -