X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=jqzIGNTaFWMQjmbbYjK+V7grK0PoH0A5qA5Elpkd2kgbekhREC8mM
	Rr0ES20XE0E6KYicPxXKMlRv/YgR/mB5wfcpN9FQdLR13gJhSPS3tYE0k2vaZ+b4
	lPIxkUeLhbr31BGwHY6UKAuRJS9s8mk1YbcSWow2kG4tl+zxEsgmRk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=bwIR2ublJpZ6NSeBH/dgMRY1W3Y=; b=sRC8LkrO+V5Gz5gDNexEOn1lTC1R
	PrPnS13AX+KWaxZa+sERodZNlXyrbrhc+8Xx2BtwC9fjiXatKgZIlWle2SJ8GXO+
	YR555Zye1A9982+gQtSYg8iGIuUW0nz42fjNAsit7EU2Le67cldZBYm5X0GuqaUH
	uFCWJE72P5OQVKM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19NCcLLrreSUX2rGox9896E
Date: Tue, 18 Jun 2013 22:02:34 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Adding MSYS functionality to Cygwin
Message-ID: <20130619020234.GA3669@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw AT mail DOT gmail DOT com> <51C0B08E DOT 8080900 AT etr-usa DOT com> <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ AT mail DOT gmail DOT com> <51C0D956 DOT 4090905 AT etr-usa DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51C0D956.4090905@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Jun 18, 2013 at 04:04:06PM -0600, Warren Young wrote:
>On 6/18/2013 13:30, ??????? ?????? wrote:
>> 2013/6/18 Warren Young <warren AT etr-usa DOT com>:
>>> On 6/18/2013 12:40, ??????? ?????? wrote:
>>>>
>>>> 1. The correct definition of executables belonging to Cygwin DLL.
>>>
>>> Can you give an example of what you mean here?
>>>
>> All cygwin applications depends on cygwin1.dll. We need to translate
>> arguments only for non-cygwin applications.
>
>It would be possible, though somewhat evil, for Cygwin's exec() 
>implementation to peek at the DLL dependency list of a program before 
>starting it, and from that infer whether it should automatically 
>translate paths.

Cygwin already does this.  It detects whether the program it is about
to run uses the Cygwin DLL and, if not, makes decisions on how to
handle exec.  It would be relatively easy to extend this.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple