[Mono-dev] Ideas for Mono on Windows

Paolo Molaro lupus at ximian.com
Thu Nov 13 09:01:00 EST 2008

On 11/11/08 Jonathan Chambers wrote:
> 1) We should consider using MSVC as the default compiler for C code on
> Windows. I can compile the entire Visual Studio solution for the runtime in
> minutes. It takes 20-30 seconds if I do a parallel build. We can also use
> the Visual Studio debugger on Windows, which IMO is betten than gdb on
> Windows.

So this is already done by you, AFAIK. I even add new .c files to the MSVC build
files (when I remember about it:).

> it). Another option is to moved to MSBuild/xbuild for the class libraries.

I think you're taking it from the wrong side.
There is no need to move the Linux build system to xbuild or whatever.
As other have mentioned, the build files can be generated from the
.sources files quite easily. You can write the conversion script in perl
or even C# and we can have rules in the makefiles to run them
automatically when the source files are modified.

AFAIK, the only two things missing are:
1) a windows developer that volunteers writing the script and
MSBuild/xbuild files.
2) a windows developer that documents the thing for other windows
developers so they are not tricked into going down the cygwin route
anymore and just click on the right buttons instead.

As you see we only need some windows developer to step up to the plate.
I suggest starting to build the complete assemblies first, without
going into the details of bootstrapping. This should take an hour or
two. And then we (mostly hari I guess) can help with the bootstrap

So, who volunteers?


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Mono-devel-list mailing list