Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3B8BB053.DE3BE44B@etr-usa.com>
Date: Tue, 28 Aug 2001 08:53:07 -0600
From: Warren Young <warren@etr-usa.com>
Organization: -ENOENT
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: On Cygwin package naming and a setup.exe bug
References: <17B78BDF120BD411B70100500422FC6309E32B@IIS000>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bernard Dautrevaux wrote:
> 
> However I must admit that, having read the original posting again, it does
> not positively says what is in the binary PRC-tools cygwin package; we just
> understand the term differently it seems.

I use PRC-Tools regularly, so let me try to add some light to this
heated discussion.  :)

I mainly use the Linux version of PRC-Tools, but the last time I used
the Windows version, it assumed that it was being installed into a
working Cygwin environment.  I'm sure this hasn't changed -- the
PRC-Tools people are only trying to change their installation
mechanism.  Since they assume a working Cygwin environment, setup.exe
should exist on users' systems, so trying to make it flexible enough to
go and fetch PRC-Tools is a reasonable thing to attempt.

The binary tools are built as patched versions of the native ones, and
they do depend on cygwin1.dll, so there is a GPL issue here, but the
PRC-Tools project is not re-distributing anything from Cygwin itself. 
It only uses Cygwin code in the distributed binaries.  

There should be no file conflicts, because the PRC-Tools are built with
entirely different prefixes.  It's a cross-compiler living on the same
system as the native compiler that built it.
-- 
= Warren -- ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m

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