[Mono-devel-list] MSVC build, fixed!
spouliot at videotron.ca
Mon Mar 7 15:03:34 EST 2005
Just a few words to say that I have been able, using your instructions and
files, to build Mono SVN HEAD using Visual Studio .NET 2005 (Dec CTP). Apart
from the new files added in 1.1, the required changes to SVN are very
similar. The results (e.g. warnings) looks the same except that LL is now
accepted for 64 bits integers and that VS.NET2K5 adds a lot more warnings
(mostly for "deprecated" functions usage). I've also added some code for the
stack walking routines (not sure it's 100% ok but it doesn't fails when
doing a stack walk for CAS).
Now I was curious if you had any updates on your side that we could merge
together before starting to move things into SVN ?
Thanks a lot for your efforts!
home: spouliot at videotron.ca
> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com
> [mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of J Lothian
> Sent: 14 fevrier 2005 11:05
> To: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-devel-list] MSVC build, fixed!
> Well, there isn't a "solution" file because it's MSVC 6, and that's a
> VS.Net thing, but the workspace can be imported into .Net just by
> opening it up and clicking "yes" a few times. ( I may provide both a
> VS 6 workspace and a VS.Net solution next release, just to
> uncomplicate things a little.)
> On Mon, 14 Feb 2005 15:06:44 +0100, Paolo Molaro <lupus at ximian.com> wrote:
> > On 02/13/05 J Lothian wrote:
> > > I had assumed there was a reason that mono was using the "this"
> > > pointer, but its a global function. Changing it to a nonreserved
> > > value, such as *thisObj works! The library now compiles, and executes!
> > > I ran test-6.exe under /embed/teste.c successfully!
> > >
> > > This was definately an upswing to a lot of hard work getting this
> > > thing together!
> > Congrats!
> > Now some notes:
> > *) you used 1.0.5 to make the changes: could you port them
> > over to 1.1.4 (to be released shortly) or better yet to the
> > current svn version?
> I'll get on it as soon as I get some free time (busy week, at the
> moment), but I may be able to have it done by next weekend. The
> reason I worked on 1.0.5 first was to minimize any errors to things I
> was doing rather than things that were just bugs.
> > *) genmdesc needs to be built as part of the build process,
> > since it depends on the currently defined opcodes etc. Using an
> > old version may make the build fail. This is less of a problem for
> > monoburg which changes much more rarely.
> The genmdesc actually has a project in the workspace that I left in
> during my final cleanup. The work it does isn't automated yet, but I
> think I can work that into my next release.
> > *) The changes to mini-exceptions.c: it's not enough to comment
> > out the code, since it would make stack walking crash: luckily
> > it's not a feature that gets used for simple tests, but you'll
> > need to find a way to implement the missing bits.
> That one is going to be a little more difficult, as I've never written
> code for stack walking before. I'll do some research, and try to get
> it working though.
> Thanks for your input everyone, this has turned out pretty well so
> far, hope the svn build doesn't give me much trouble so I can get that
> out and working, I'd love for these changes to be in a release, make
> it easier for anyone that wants to use VS to develope in.
> -J Lothian
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list