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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <5.1.0.14.0.20031013193743.02ecc898@127.0.0.1>
X-Sender: 
Date: Mon, 13 Oct 2003 19:43:15 -0400
To: Edward Peschko <esp5 AT pge DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: merging mingw and cygwin
Cc: cygwin AT cygwin DOT com
In-Reply-To: <20031013224522.GB26012@mdssirds.comp.pge.com>
References: <bmf8as$kg7$1 AT sea DOT gmane DOT org>
 <20031012052757 DOT GB12191 AT mdssirds DOT comp DOT pge DOT com>
 <1065936902 DOT 844 DOT 19 DOT camel AT localhost>
 <20031012062347 DOT GA12677 AT mdssirds DOT comp DOT pge DOT com>
 <bmeida$gnh$1 AT sea DOT gmane DOT org>
 <20031013190000 DOT GB20245 AT mdssirds DOT comp DOT pge DOT com>
 <bmf0hl$fvb$1 AT sea DOT gmane DOT org>
 <20031013203527 DOT GA25036 AT mdssirds DOT comp DOT pge DOT com>
 <bmf39l$ls2$1 AT sea DOT gmane DOT org>
 <20031013213226 DOT GC25036 AT mdssirds DOT comp DOT pge DOT com>
 <bmf8as$kg7$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 06:45 PM 10/13/2003, Edward Peschko you wrote:
>> Just because they are available does not mean you need to use them! Look 
>> I asked you if you were able to build Windows only applications using 
>> -mno-cygwin. You failed to answer that question. I'm able to build such 
>> apps and you should be too. You are arguing about the differences in 
>> implementations and assuming that there will be a problem. Is there a 
>> problem for you or not?
>
>Like I said, I'm not worried about my specific applications. I want cygwin
>to transparently and with no fuss - and correctly - build third party APIs,
>so I can properly link with them (and debug them if necessary).
>
>> We can speculate from now until forever but until and unless you try it 
>> you'll never know for sure. Let us know how you make out...
>
>I did try it. With berkeleydb.  Read my previous post.
>
>> Not sure what msys is at all...
>
>msys is the group of tools that comes with mingw32 to facilitate building.
>rm, ln, etc. They work differently than cygwin tools.
>
>> >MINGW and/or NO_CYGWIN simply wrap all of this up in a nice user friendly 
>> >package.
>
>> Let us know how your first implementation of this concept goes...
>
>Is this an OK from the developers of cygwin to do an implementation, with 
>the results of that implementation being merged into cygwin? I don't want 
>to spend a lot of time pursuing it if my results don't have a chance of being
>merged.
>
>The last time I asked, the answer was no to this question.


The answer is - the Cygwin team is under no obligation to accept patches
to Cygwin to do anything.  Patches are accepted and merged based on merit 
of the patch and adherence with Cygwin standards.  If your patch passes 
these hurdles, it will be accepted.  If not, it will be rejected (with 
comments of course so you may very well be able to address the issues and
"resubmit").  No one will pre-approve a concept.  We need to see code.



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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