I did read reason 2. But I thought that mono-build-w32.sh was for Windows/Cygwin machines only?
Or am I incorrect about that?
-----Original Message-----
From: Dick Porter [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 2:28 PM
To: '[EMAIL PROTECTED]'
Subject: Re: [Mono-list] make: Nothing to be done for `all'.
On Mon, Apr 15, 2002 at 10:26:10AM -0400, Kenneth Benson wrote:
> I can see why you wouldn't put it in the mono-build.sh script for Linux, but
> why not put it in the mono-build-w32.sh since that's for win/cygwin?
Did you not read reason 2)?
Just in case, I'll leave it quoted.
- Dick
>
> -----Original Message-----
> From: Dick Porter [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 14, 2002 7:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Mono-list] make: Nothing to be done for `all'.
>
>
> > the mono runtime builds alright, but it doesn't run without the mcs
> > libraries, so why not add the statements to checkout and build mcs in the
> > mono-build-w32.sh script?
>
> Because
>
> 1) the mcs dir builds without any trouble (no dependencies or sacrificial
> chickens required).
>
> 2) the mcs dir currently does not build on linux, so the two scripts will
> be doing different tasks on different platforms.
>
_______________________________________________
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
