Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	<033101c2cd3f$4f2936d0$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Nigel Stewart & Fiona Smith" <nigels AT nigels DOT com>,
	"Jay Maynard" <jmaynard AT conmicro DOT cx>, "cygwin" <cygwin AT cygwin DOT com>
References:	<20030204194653 DOT A5738 AT thebrain DOT conmicro DOT cx> <Pine DOT GSO DOT 4 DOT 44 DOT 0302042115170 DOT 24195-100000 AT slinky DOT cs DOT nyu DOT edu> <20030204204803 DOT A6191 AT thebrain DOT conmicro DOT cx> <20030205033246 DOT GA4959 AT redhat DOT com> <20030205111822 DOT B9661 AT thebrain DOT conmicro DOT cx> <3E414A63 DOT 6060608 AT nigels DOT com>
Subject:	Re: Packaging software built with cygwin
Date:	Wed, 5 Feb 2003 17:52:11 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Nigel Stewart & Fiona Smith wrote:
>> 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.

If someone wishes to volunteer to work towards that...

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

I believe this would require some significant work to make it possible.

> However, is it feasible for the Cygwin project to
> make this exception for the sake of utility?

If you are talking about making cygwin static-capable - see above - lots of
work. Also, the most experienced Cygwin coders won't be that interested,
because they *like* Cygwin-the-enviroment, as opposed to
Cygwin-for-the-sake-of-one-program.

Also, there is the side benefit that it is *much* easier to spot GPL
violations this way.

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

You can - they just can't use the unix APIs.
I use Cygwin for all my compilation needs, Cygwin-linked, or native Win32.

Max.


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

- Raw text -