Larry Hall (Cygwin) sent the following at Friday, March 18, 2011 6:01 PM
>On 3/18/2011 2:39 PM, Alex Khripin wrote:
>> Short summary: getting nested quotes in an argument through to a
>> Cygwin process from DOS is problematic, and there does not seem to beif you
>> must
>> any detailed spec for ho
On Fri, Mar 18, 2011 at 11:47:12PM -0400, David Boyce wrote:
>On Fri, Mar 18, 2011 at 6:00 PM, Larry Hall (Cygwin) wrote:
>> On 3/18/2011 2:39 PM, Alex Khripin wrote:
>> If you're using a native Windows 'make' with a Cywgin shell, you're better
>> off making your tools consistent. ?Quoting mechanis
On 3/18/2011 11:47 PM, David Boyce wrote:
> From the README.W32 file in the source package:
>
>Good news! Make now has native support for Cygwin sh. To enable,
>define the HAVE_CYGWIN_SHELL in config.h and rebuild make
>from scratch. This version of make tested with B20.1 o
On Fri, Mar 18, 2011 at 6:00 PM, Larry Hall (Cygwin) wrote:
> On 3/18/2011 2:39 PM, Alex Khripin wrote:
> If you're using a native Windows 'make' with a Cywgin shell, you're better
> off making your tools consistent. Quoting mechanisms for Windows do not
> align with those used by Cygwin/Linux/Uni
On 3/18/2011 2:39 PM, Alex Khripin wrote:
Hi,
Short summary: getting nested quotes in an argument through to a
Cygwin process from DOS is problematic, and there does not seem to be
any detailed spec for how to escape quotes correctly. Backslash
characters seem to be spuriously generated.
If yo
Hi,
Short summary: getting nested quotes in an argument through to a
Cygwin process from DOS is problematic, and there does not seem to be
any detailed spec for how to escape quotes correctly. Backslash
characters seem to be spuriously generated.
I'm working on a build system (GNU make, Windows b
6 matches
Mail list logo
