DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=jMnrQAu6VrfKASOyh9/7S/dU0asBh
	vBsAX68g7Kkc8VYledP0SVkE0tKwz6JxgMmx7AVhslIrSKeY4PSYY9vMn1oaE5zl
	3zzxNrycEGH3nx+nVqqTLlV94AjD1kQebTfi2u9hHA2Hc+pnaOz1HppvuABAc6Id
	W4G6pfeXY0P+sY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: Kal Sze <swordangel@gmail.com>
Date: Wed, 5 Nov 2014 16:18:34 +0800
Message-ID: <CAGZiy731mOGON-Bhd9XYZo-8jQ0WrLKOioxKBGnJrZbDprGvPg@mail.gmail.com>
Subject: Running non-cygwin executables in cygwin bash terminal or script
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

Hello,

In general, is there anything that can go wrong or not work if I
invoke regular Windows/.NET executables (not compiled with any cygwin
header or linked with any cygwin dll) from a cygwin bash terminal or
script?

I am planning to write a bash script to call rsync and then a command
line program written in C# (.NET framework 4.5 in Visual Studio 2013).

I'm not a huge cygwin/posix/unix hacker, so there are a few things
that seem murky. I suppose that are other people in similar
situations.

I can think of a few things that don't seem entirely clear in the
documentation and FAQ.

I'm guessing that invoking regular Windows/.NET executables would
mostly just work, with the following caveat:
- stdin/stdout/stderr redirection and piping would still work, even
when piping with cygwin-linked programs (care with charset and
end-of-line conventions needs to be taken, however);
- UNIX-style sockets are out of the question;
- the usual Window permission model would still be used;
- if the regular Windows/.NET executable accepts a file or directory
path as argument, it still needs to be written in the Windows style
(i.e. "C:\\foobar\\" instead of "/cygdrive/c/foobar");
- the locale of the cygwin bash process may cause problems when
passing arguments to the regular Windows program.

Am I mostly correct? So far it seems to work. Am I missing other caveat?

Would it make sense to have all this summarized in the FAQ?

Best Regards,
Kal

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