[Mono-list] MCS build failure

Nick Drochak ndrochak@gol.com
Wed, 5 Feb 2003 15:31:22 +0900

| -----Original Message-----
| From: John BouAntoun [mailto:John.BouAntoun@rogen.com.au]
| Sent: Wednesday, February 05, 2003 12:25 PM
| To: Nick Drochak
| Subject: RE: [Mono-list] MCS build failure
| But doesn't using csc sort of make the self hosting statement invalid?

Perhaps I should have been more clear. I didn't mean to make any statements
invalid :).

We have a build that runs on cygwin on Windows that uses csc and MS .NET and
provides, among other benefits, a verification for the build that runs on
mono (*nix or Windows). This doesn't have anything to do, per se, with self
hosting. This build uses some makefile(s) and some .build files with NAnt
and assumes csc and MS .NET.

We have a separate build system made entirely of makefile.gnu(s) that
assumes mono and mcs. This build system is the self hosting one.

At least that's the way I understand it.

| Isn't there an easy way to specify which csharp compiler?
| Like maybe "export CSHARPCOMPILER = /usr/local/bin/mcs.exe"  or something?

I don't know how smart we can make the build system, but I would like to
just say one of these:
  'make runtime=mono'  <== this defaults to using mcs
  'make runtime=dotnet'  <== this defaults to using csc
  'make runtime=dotnet compiler=mcs' <== to override the default

and the makefile knows what to do. Perhaps the system could also allow one
to tweak things, such as the exact mcs binary image to use as you suggest

This would be quite handy for different test scenarios and verification

I'm not very good with makefiles, or I would have tried to set this up
myself long ago ;)

Nick D.

P.S. did you mean to just reply to me?  Perhaps this should go to the
mono-list as well?