Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3E414A63.6060608@nigels.com> Date: Thu, 06 Feb 2003 04:31:15 +1100 From: Nigel Stewart & Fiona Smith User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jay Maynard , cygwin Subject: Re: Packaging software built with cygwin References: <20030204194653.A5738@thebrain.conmicro.cx> <20030204204803.A6191@thebrain.conmicro.cx> <20030205033246.GA4959@redhat.com> <20030205111822.B9661@thebrain.conmicro.cx> In-Reply-To: <20030205111822.B9661@thebrain.conmicro.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit > I would suggest that, if it is desired to promote the development of > applications on the Cygwin platform, serious consideration be made to making > it as simple as possible to install only those portions of Cygwin that the > application requires. This means just the necessary DLLs, without all of the > interactive use baggage. Right now, that's nearly impossible. Technically, the ideal solution would be to link against a set of static libraries. Therefore requiring no extra install at all. No DLL hell, no tech support, no "Cygwin is the problem" perception. However, is it feasible for the Cygwin project to make this exception for the sake of utility? This is the same reason I find myself experimenting with mingw, I would like to use Cygwin as the devel platform and target native binaries, or at least non Cygwin-DLL dependent binaries... My 0.02, no offence intended to GPL oriented people... Regards, Nigel Stewart -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/