[WIP] Get rid of msys in favor of busybox port for windows

[WIP] Get rid of msys in favor of busybox port for windows

[Nguyen Thai Ngoc Duy]

Hi,

I'm integrating some code from busybox to mingw tree so that mingw
port can work without msys. Posix utilities such as sed, awk, head,
tail... seem to work well. The main obstacle is ash, which is no where
near usable state (fork issues as always). Busybox ash is about 13000
lines of code, not too big.

Anyone interested in?
-- 
Duy

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Johannes Schindelin]

Hi,

On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:

> I'm integrating some code from busybox to mingw tree so that mingw port 
> can work without msys. Posix utilities such as sed, awk, head, tail... 
> seem to work well. The main obstacle is ash, which is no where near 
> usable state (fork issues as always). Busybox ash is about 13000 lines 
> of code, not too big.
> 
> Anyone interested in?

Definitely.

Last time I wanted to assess how much work it is to compile that on MinGW, 
though, it seemed to be too much to be tractable.

Ciao,
Dscho

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Nguyen Thai Ngoc Duy]

On 7/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:
>
> > I'm integrating some code from busybox to mingw tree so that mingw port
> > can work without msys. Posix utilities such as sed, awk, head, tail...
> > seem to work well. The main obstacle is ash, which is no where near
> > usable state (fork issues as always). Busybox ash is about 13000 lines
> > of code, not too big.
> >
> > Anyone interested in?
>
> Definitely.
>
> Last time I wanted to assess how much work it is to compile that on MinGW,
> though, it seemed to be too much to be tractable.

The exact answer is "I don't know" :-) I cross compile all the time
however it should build fine on MinGW as it now uses git Makefile.
I'll push the patch into mob soon.
-- 
Duy

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Johannes Schindelin]

Hi,

On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:

> On 7/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > 
> > On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:
> > 
> > > I'm integrating some code from busybox to mingw tree so that mingw port
> > > can work without msys. Posix utilities such as sed, awk, head, tail...
> > > seem to work well. The main obstacle is ash, which is no where near
> > > usable state (fork issues as always). Busybox ash is about 13000 lines
> > > of code, not too big.
> > >
> > > Anyone interested in?
> > 
> > Definitely.
> > 
> > Last time I wanted to assess how much work it is to compile that on MinGW,
> > though, it seemed to be too much to be tractable.
> 
> The exact answer is "I don't know" :-) I cross compile all the time
> however it should build fine on MinGW as it now uses git Makefile.
> I'll push the patch into mob soon.

Do you mean the whole busybox thing?

If so, please do not put it into mingw.git.  Rather, start a busybox.git 
project (I saw that you have already some projects on repo.or.cz, so it 
should be easy for you.)

Thanks,
Dscho

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Nguyen Thai Ngoc Duy]

On 7/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:
>
> > On 7/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > >
> > > On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:
> > >
> > > > I'm integrating some code from busybox to mingw tree so that mingw port
> > > > can work without msys. Posix utilities such as sed, awk, head, tail...
> > > > seem to work well. The main obstacle is ash, which is no where near
> > > > usable state (fork issues as always). Busybox ash is about 13000 lines
> > > > of code, not too big.
> > > >
> > > > Anyone interested in?
> > >
> > > Definitely.
> > >
> > > Last time I wanted to assess how much work it is to compile that on MinGW,
> > > though, it seemed to be too much to be tractable.
> >
> > The exact answer is "I don't know" :-) I cross compile all the time
> > however it should build fine on MinGW as it now uses git Makefile.
> > I'll push the patch into mob soon.
>
> Do you mean the whole busybox thing?
>
> If so, please do not put it into mingw.git.  Rather, start a busybox.git
> project (I saw that you have already some projects on repo.or.cz, so it
> should be easy for you.)

No, I don't port the whole busybox (too big, too difficult). I
extracted stuffs that need to run shell scripts (mainly coreutils and
ash) and put them in my mingw tree. Just wanted to push it if you
wanted to try.. maybe later.

-- 
Duy

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Henning Rogge]

On 7/10/07, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> I'm integrating some code from busybox to mingw tree so that mingw
> port can work without msys. Posix utilities such as sed, awk, head,
> tail... seem to work well. The main obstacle is ash, which is no where
> near usable state (fork issues as always). Busybox ash is about 13000
> lines of code, not too big.
>
> Anyone interested in?
If I can use it without needing a "vi/vim" implementation I'm interested !

Henning

Re: [WIP] Get rid of msys in favor of busybox port for windows

[Nguyen Thai Ngoc Duy]

On 7/10/07, Henning Rogge <hrogge@googlemail.com> wrote:
> On 7/10/07, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> > I'm integrating some code from busybox to mingw tree so that mingw
> > port can work without msys. Posix utilities such as sed, awk, head,
> > tail... seem to work well. The main obstacle is ash, which is no where
> > near usable state (fork issues as always). Busybox ash is about 13000
> > lines of code, not too big.
> >
> > Anyone interested in?
> If I can use it without needing a "vi/vim" implementation I'm interested !

There is no vi/vim in the port :-) My goal is to make shell scripts
work with minimum effort. I don't even attempt to make ash
interactively usable (well, git add --interactive and friends have to
wait longer).
-- 
Duy