[Mono-dev] Build MONO under VS2005

[Sebastien Pouliot]

Hello Aras,

On Fri, 2006-04-21 at 18:42 +0200, Aras Pranckevicius wrote:
> > > Yep, that's exactly what I was observing.
> >
> > Now I wonder if this is a VS2005 or VS2003 related problem...
> 
> I guess the biggest reason is that most of VC project files are
> missing. I checked right now in 1.1.15, and I can only see mono.sln,
> genmdesc.vcproj, libmono.vcproj and mono.vcproj. 

It's possible that some files are missing from the source tarballs (I
never used them to compile under VS.NET).

> VSDependencies also does not contain the projects. 

and that's not their place.

> Last time I checked they were not in the svn either. 

but everything is in SVN and has always been (well since the solution
file was added), including:

genmdesc.vcproj
libmono.vcproj
mono.vcproj
samples\embed\test-invoke.vcproj
samples\embed\teste.vcproj
samples\embed\test-metadata.vcproj
libgc\libgc.vcproj
mono\dis\monodis.vcproj
mono\pedump.vcproj
mono\monodiet.vcproj
mono\monoburg\monoburg.vcproj
mono\monograph\monograph.vcproj

> That makes me wonder how exactly people have succeeded
> compiling mono, but oh well :)

wonder no more ;-)

> > cygwin is required/useful for
> > * autogen, which creates some required files;
> > * running some tools, like genmdesc and monoburg;
> > * testing the results (runtime tests);
> > * building the class libraries (and running the unit tests);
> > The last two items make cygwin worth installing
> 
> Yes. Except if you don't install it for religious reasons!

Yeah, that's a difficult one to object, but I've heard some other good
reasons too ;-)

> Getting genmdesc and monoburg to run only required bison and some
> custom build rules in Visual Studio. 

That would make a wonderful addition to the wiki :-)

> That was even faster than setting
> up cygwin for me. And we only embed mono, so a compiled libmono is all
> I ever need.
> 
> > Optimization affecting the stack frames have been reported to cause
> > problems. Of course other things may cause problems too.
> 
> Yes, that is the place that required some VS specific pragmas (stack
> frames) in some places. 

That would be nice to know.

> Other than that, libmono just works. And the
> produced dll size is smaller than the one built by cygwin - that's
> something that really matters for us.

I'm glad it is useful. Let us know if you find VS.NET specific problems
(and their solutions :-).

Have a nice weekend!
-- 
Sebastien Pouliot  <sebastien at ximian.com>
Blog: http://pages.infinit.net/ctech/