From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17506 invoked by alias); 8 Jun 2004 13:02:30 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 17482 invoked from network); 8 Jun 2004 13:02:27 -0000 Received: from unknown (HELO cgf.cx) (66.30.22.40) by sourceware.org with SMTP; 8 Jun 2004 13:02:27 -0000 Received: by cgf.cx (Postfix, from userid 201) id CA2E840065B; Tue, 8 Jun 2004 09:02:21 -0400 (EDT) Date: Tue, 08 Jun 2004 13:02:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Visual Studio linking Message-ID: <20040608130221.GA524@coe.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040607162514.GB4767@coe.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2004-06/txt/msg00323.txt.bz2 On Tue, Jun 08, 2004 at 10:02:08AM +0100, Alastair Growcott wrote: >Actually my source is testing a library, so if I did distribute the >test programs, I would only have to make the code for the test programs >and not the code for the libraries available (dynamic linking to the >libraries). As long as you don't release the cygwin DLL... If you do, you need to provide sources, too. 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/