From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: On Cygwin package naming and a setup.exe bug
Date: Tue, 28 Aug 2001 07:53:00 -0000 [thread overview]
Message-ID: <3B8BB053.DE3BE44B@etr-usa.com> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E32B@IIS000>
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/
next prev parent reply other threads:[~2001-08-28 7:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 13:03 Bernard Dautrevaux
2001-08-28 7:53 ` Warren Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-29 9:20 jmarshall
2001-08-29 10:10 ` Michael F. March
2001-08-29 10:59 ` Alex Malinovich
2001-08-29 11:02 ` Charles S. Wilson
2001-08-29 14:04 ` Michael Schaap
2001-08-29 6:35 Bernard Dautrevaux
2001-08-29 7:37 ` Christopher Faylor
2001-08-29 6:12 Bernard Dautrevaux
2001-08-29 6:25 ` Robert Collins
2001-08-29 7:35 ` Christopher Faylor
2001-08-27 11:16 Bernard Dautrevaux
2001-08-27 11:42 ` Charles Wilson
2001-08-27 11:54 ` Christopher Faylor
2001-08-27 11:03 Bernard Dautrevaux
2001-08-27 11:37 ` Christopher Faylor
2001-08-26 0:51 John Marshall
2001-08-26 10:46 ` Christopher Faylor
2001-08-27 3:39 ` Warren Young
2001-08-27 10:39 ` Christopher Faylor
2001-08-27 10:52 ` Charles Wilson
2001-08-28 0:14 ` Robert Collins
2001-08-28 6:00 ` John Marshall
2001-08-29 7:30 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B8BB053.DE3BE44B@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).