Tue, 23 Jul 2013 01:16:32 +0800, Thorsten Glaser <[email protected]> wrote:
Fabian Greffrath dixit:
In the end I found MSYS and stick with it until today. It is an early
fork of Cygwin by the people who develop MinGW and provides just enough
of a shell and tools to run ./configure scripts.
Right. It’s pretty hard to develop _for_ MSYS really, but stock
(Unix) mksh builds against it out-of-the-box thanks to, I think,
RT from IRC. (If I mis-remember, sorry.)
I did nothing about porting mksh to MSYS(since it was ready to work in
MSYS before I test and state it)
I'd suggest to give it a try and maybe bundle it with mksh/Win32 to
With MSYS I’d rather bundle (Unix) mksh built against MSYS into
their distfiles (it’s mksh which is the stand-alone, separate,
portable thing that can be bundled with others, not the other
way around).
provide a better and more complete shell environment. I am not sure if
It will, yes, but this is half-way orthogonal to mksh/Win32,
which fits with people not wanting to install half a Unix
environment. (Basically, if you consider “something like Cygwin”
you can just build stock Unix mksh for it; this will then use
its normal console I/O for example, whereas mksh/Win32 will use
the WinAPI functions – but (quick idea of mine, didn’t talk with
Michael about it yet) it could use the wide character versions
of those APIs and just present it to edit.c appropriately,
instead of having to deal with codepages and stuff.)
In short, there’s a spectrum of “environments” in which one
could use mksh on “some sort of NT”:
^
|
native WinAPI
|
MinGW
|
|
|
|
|
PW32
|
|
UWIN
|
MSYS
|
Cygwin
|
|
SUA (Server 2008 R2)
|
SFU/Interix 3.5
|
|
CoLinux
|
VMware/VirtualPC/etc.
|
v
You can plug it in anywhere there, but it won’t be the same
(e.g. I hold the rule “no special handling for drive letters
or CR/LF line ends” strict for MSYS mksh but (other than
asking to also not handle CR/LF as newline) haven’t yet
restricted mksh/Win32 that way).
So there is a separated patch to workaround this(about capturing
win32/mingw program outputs)
http://permalink.gmane.org/gmane.os.miros.mksh/43
there are other alternatives (I believe I have once read about a
busybox.exe for W32), but I have tried UnxUtils, Cywin and MSYS and
I made it to my personal goal to get rid of ash in all its
variants; busybox’ ash is about middle of the bad-worse-worst
playing field though. I think mksh fills the place of an sh
component pretty well. (And indeed, Android uses it alongside
their “toolbox” and mksh can be used as “beastiebox”’ shell
component.)
But that’s neither here nor there ;-)
Thanks for your interest and feedback,
//mirabilos
