[Mono-dev] Compiling mono on windows for developing (not running)
monoforum at my2cents.co.uk
Sat Apr 26 09:37:25 UTC 2014
I'll have to wait until someone puts a guide together about developing on
windows as I am seriously out of my depth. I've spent about 2 evenings so
far trying to get mono to build in cygwin, but coming up with various
errors that googling isn't solving.
It's disappointing that it appears there is little appetite for getting
extra people to help with mono who don't own a mac (the whole reason I host
on mono is because I'm skint so no chance of me affording a decent mac,
even if I wasn't an apple hater).
I'm actually starting to think that it may be worth looking at alternatives
due to the fact there isn't really any interest in getting Asp.Net side of
things up and running.
Not saying Asp.Net is dead as < MVC4 is working fine, but it does appear to
be being put to pasture after the creation of Xamarin. Lots of pulls
either taking a long time to merge, or just being ignored.
Anyway, rant over, thanks for the response.
On 26 Apr 2014 02:05, "Edward Ned Harvey (mono)" <
edward.harvey.mono at clevertrove.com> wrote:
> > From: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-
> > bounces at lists.ximian.com] On Behalf Of Martin Thwaites
> > As a side question, what is the tool that the rest of you use to develop
> > mono? do you develop on windows or on Linux?
> I spent some time on this not long ago, and it's rather frequent that we
> hear questions from people who want to develop mono sources, having trouble
> getting it to build, or attaching debugger to it, etc. You *might* not be
> far off, getting it to build in VS, but for a while now, there's been a
> steady stream of people (including myself) who started by asking the same
> question, and before too long, found it easier to adapt to the system
> instead of the other way around. I know I didn't try too hard, and I don't
> know if anyone else has. So it *might* be easy-ish, or it might be an
> insurmountable obstacle.
> There has been some talk about improving the build process, making it
> easier to adopt new developers, and it seems that Miguel is diving into it,
> but more for the purpose of untangling some mess and making the process
> more reliable, less for the sake of making it easier for new devs. Lots of
> times, improvements come out of efforts like those, as a positive side
> effect, but it's yet to be seen.
> I will say: Getting monodevelop (xamarin studio) to work on windows is
> trivial. But in order to do some good debugging, you'll want to build the
> sources too. And as you're discovering, that's a little tougher on windows.
> Getting XS on mac is trivial. Installing mono MDK on mac is trivial.
> Building mono for the first time required a little bit of prep (XCode,
> command line tools, homebrew, autoconf, automake, libtool). But after
> that, building on the mac and developing in XS is quite nice. (Sorry, no
> resharper... XS isn't as good as VS, but XS is quite good nonetheless.)
> If you don't have a mac, I'll encourage at least a *little* bit of effort
> getting windows to build - via cygwin, not the sln.
> But unfortunately, you're going to have to lower your expectations. I
> find, even when I have everything working, there are lots of shortcomings
> in debugging. Like... I create some class or call some method. I step
> into. And the debugger goes to outerspace. Or I step into, and when I get
> there, all the code is grayed out and I cannot inspect any variables, but
> if I'm lucky, I can at least continue stepping. Sometimes can't. And
> various little weird behaviors like that. And every time you make a
> change, you have to "make" again. There goes 5min to 30min, depending on
> what you changed.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list