[Mono-dev] Build MONO under VS2005
sebastien.pouliot at gmail.com
Fri Apr 21 08:02:27 EDT 2006
On Fri, 2006-04-21 at 12:02 +0200, Aras Pranckevicius wrote:
> > The problem is indicated as genmdesc.vcproj, libmono,test -invoke.vcproj...
> > are not installed. I did copy the VSDependencies.zip and copy it under
> > /mono/directory ... but it did not work to me.Additionally, I did install
> > working cypwin as well and did all the steps to build mono.Additionally,
> > VS2005 compiler indicated " solution folders are not supported in this
> > version of Visual Studio" ?????
> Yep, that's exactly what I was observing.
Now I wonder if this is a VS2005 or VS2003 related problem...
> What I did was just make VS2003 (not using 2005 here yet) projects
> from scratch.
The original contributed patch (which can be found in the mailing-list
archives) was for VC 6. So there's no reason it shouldn't work using
VS2003 (or even VS2002) with a few modifications. VS2005 (some beta) was
selected because this is what I had on my XP computer at the time.
> And I made it not require cygwin (just bison for
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 :)
> So far we have no problems running Visual Studio
> compiled mono in release mode.
Optimization affecting the stack frames have been reported to cause
problems. Of course other things may cause problems too.
IMHO the big gain of using VS.NET is the debugger (and other debugging
tools). So the release build wasn't a very interesting target to test.
> Someone should push me strong enough to find some time and contribute
> the project files back I guess :)
<push force="strong" action="contribute"/>
Sebastien Pouliot <sebastien at ximian.com>
More information about the Mono-devel-list