[Mono-list] Re: Mono on Windows Primer?

Francisco T. Martinez martinf@mfconsulting.com
Sun, 15 Aug 2004 12:02:22 -0500

Craig Dayton wrote:

>Hi Franciso,
>Thanks for the response and the pointers to other resources.  I'll check
>them out carefully.
>When I attempted to compile MSC (1.0.1) using VS .Net 2003, it errors with
>unable to find 'cs.parser.cs'. Searching through the source distribution,
>there is a file titled 'cs.parser.jay' but when renamed to the missing file
>more errors are generated on the compulation.  I thought MSC was self
>hosting which from my reading meant it should be able to compile itself.  I
>didn't find any instructions on how to get MSC to compile itself without
>resorting to installing cygwin or some other Unix based utilities.
>Along with the problem above and the apparent problems with the components
>installed from the Windows installer has lead me to believe there are some
>issues to over come for the Windows environment.
>Hopefully, the resources you've pointed out will guide me through the
>process of compiling the various Mono components be it CLI or IDE method of
>doing so.
>Thanks Again, Craig

Building the core Mono components like the Runtime and/or the C# 
compiler (mcs.exe) from Windows is not for everyone.  Today the Win32 
version of Mono are built using cygwin.  The build process is a moving 
target as well -- this has more to do with the dynamic nature of cygwin 
and its packages.

All of the installer for windows that I have put together to this date 
have basically assemble and extended the binary Mono components that 
have resulted from the efforts of Novell employee's compilation of Mono 
for Windows.  By the way, today there is only one official builder of 
Mono for Windows at Novell and he is a dedicated resource on other areas 
of Mono functionality.

If you are just getting started with Mono on Windows I would suggest you 
build applications using Mono rather than trying to build Mono itself.