DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:subject:mime-version:content-type
	:content-transfer-encoding:date:from:cc:in-reply-to:references
	:message-id; q=dns; s=default; b=DkuGWb0lmCnI/gZ4vuXeJtIz4iJSDaQ
	zRUZd0OTT7tgn1vDS4E8ZeQrlh8x/r4mVnI8zLKQphqmFLwRG45yYyWsW/9c2fwk
	ihae8f4urWBLa2J5zWL8jChahfVKs+P6vgccksXDlQWa11ky3YKT1/aZgEVSA76e
	G9t6OYbVBBcY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: michel.labarre@rogers.com
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by  CYGWIN
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Date: Fri, 05 Aug 2016 09:22:03 -0700
From: Kaz Kylheku <kaz@kylheku.com>
Cc: cygwin@cygwin.com
In-Reply-To: <001001d1edf1$a4e1ae90$eea50bb0$@rogers.com>
References: <001001d1edf1$a4e1ae90$eea50bb0$@rogers.com>
Message-ID: <c7a70d9a03af65f97643f6dff60c560d@mail.kylheku.com>
User-Agent: Roundcube Webmail/0.9.2
Content-Transfer-Encoding: 8bit

[private, off-list reply]

Hi Michael,

Do you have some sort of list of detailed requirements implemented by 
MKS
tools where Cygwin is different or lacking in some way?

Maybe Cygwin could pick up some of them.

Anyway, about a month ago, when I learned that Cygwin is now under
the Lesser GPL, I started a project called Cygnal (Cygwin Native
Application Library) whose goal is to improve the usefulness
of Cygwin for Windows development.

http://www.kylheku.com/cygnal

However, I have a different angle on it: the perspective is
of developing a native application (which ships native executables,
without any apparent POSIX environment with a shell, commands or any
of that).

I don't need to infuse the Cygwin environment with Windows conventions;
building my program within the POSIX conventions suits me just fine.

However, I don't want the *users* of the program (a binary .exe
accompanied by .dll files, wrapped up in an installer) to be exposed
to POSIX conventions.

With Cygnal, you can develop a single executable file, which works
with POSIX and Windows conventions, simply based on which flavor
of the cygwin1.dll it is linking against.

Cheers ...


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