This is the mail archive of the
mailing list for the Cygwin project.
Re: Adding MSYS functionality to Cygwin
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Jun 2013 22:02:34 -0400
- Subject: Re: Adding MSYS functionality to Cygwin
- 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>
- Reply-to: cygwin at cygwin dot com
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 <email@example.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
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple