[MonoDevelop] MonoDevelop on Win32

Carlos J. Muentes carlos at rockwithme.org
Tue Jun 27 11:52:54 EDT 2006


Why not just use Linux?  Also, SharpDevelop has support for Mono, why
not use that?


> -------- Original Message --------
> Subject: Re: [MonoDevelop] MonoDevelop on Win32
> From: "Levi Bard" <taktaktaktaktaktaktaktaktaktak at gmail.com>
> Date: Tue, June 27, 2006 11:35 am
> To: "Daniel Morgan" <monodanmorg at yahoo.com>, monodevelop
> <monodevelop-list at lists.ximian.com>
> 
> > I am trying to build MonoDevelop on Windows.  I am having difficulting.
> >
> > If anyone has gotten it to build and run, can you please email this list
> > explaining what you did to get it to work?  I so much want it to run on
> > Windows.
> >
> > I do know Zac Bowling over a year ago got it to work, but it was
> > un-deployable.  Paco got it to work, but he didn't get past the Splash
> > screen.   I heard someone named Tak got it to load up stetic and such.
> >
> > For me,  I have got it to build, but my mono, gtk#, and cygwin environment
> > is like a big junk yard.  It's not something reproducible nor nothing you
> > would want to deploy.  I did get it to run with the splash screen popping,
> > but it eventually fails.
> >
> > I did notice it still uses unix domain sockets even though there is a
> > --ipc-tcp option when running MonoDevelop.  Once you change that to a TCP
> > InterNetwork socket, it runs the splash screen.
> >
> > The UNMANAGED_DEPENDENCIES_MONO I had earlier was because pkg-config could
> > not find my mono.pc file.  This was resolved by setting PKG_CONFIG_PATH to
> > point where my .pc files are located.  For me this was:
> >
> > export
> > PKG_CONFIG_PATH=/cygdrive/g/MonoX-1.1.13.1/lib/pkgconfig
> >
> > I was able to verify this would work by:
> >
> > pkg-config --cflags --libs mono
> 
> I've gotten it to build, and barely run on win32.  It's not anywhere
> near stable or useful yet, let alone deployable.  It will load through
> the splash screen, to the main window, allow me to create new projects
> and open existing ones (although not edit source or build yet), and
> browse the monodocs.  So far, I can not use Stetic, nor the Welcome
> Page addin.
> 
> I started where you did, with paco's installers for mono/gtk# and
> gecko#, as well as the shellter build of evolution-win32.  I built MD
> from anonymous svn rev 62063.
> 
> I have:
> GECKOSHILLA_BASEPATH=C:\Program Files\Common Files\gtkmozembed-win32
> LD_LIBRARY_PATH=/cygdrive/c/Program
> Files/Evolution/bin:/cygdrive/c/mono/MonoX-1.1.13.1/bin:/cygdrive/c/GTK/2.8/bin
> PKG_CONFIG_PATH=c:\gtkstuff\lib\pkgconfig:c:\mono\MonoX-1.1.13.1\lib\pkgconfig
> 
> I temporarily disabled the code in
> Core/src/MonoDevelop.Ide/MonoDevelop.Ide.Gui/IdeStartup.cs that checks
> for/reconnects to existing instances (UNIX sockets), temporarily
> removed the Stetic (MonoDevelop.GtkCore) and WelcomePage addins (from
> build/AddIns), and ran with --ipc-tcp.
> 
> I hope some of this is helpful.
> 
> -- 
> Tcsh: Now with higher FPS!
> http://www.gnu.org/philosophy/shouldbefree.html
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list



More information about the Monodevelop-list mailing list