Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Aug 2015 22:47:29 -0700
From:      Russell Haley <russ.haley@gmail.com>
To:        mono@freebsd.org, Ivan Radovanovic <radovanovic@gmail.com>
Subject:   MonoDevelop 5.10 for FreeBSD 10.1
Message-ID:  <CABx9NuQGnE7o3xRFYe62WSMmNQQMPm=s6Oajmhw1-JDb0ib=_Q@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Hi Guys,

So I have been able to build MonoDevelop 5.10 from Git using the current
ports version of mono. I have one item that I will submit as a pull request
to Xamarian on Github.   The following is a list of all the outstanding
items I think we have control over:

1) mono
  - There is a bug in KqueueWatcher class (KqueueEvents.cs) that causes
MonoDevelop to crash. It can be mitigated with a env variable

      *setenv MONO_MANAGED_WATCHER true*

    Ivan Radovanovic is working on a fix.

  - During the mono installation, we need to run the following command:

      *mozroots --import --syn*c

    Otherwise the MonoDevelop build fails on the restore-packages target. I
suggested it in the MonoDevelop build but the repository owner indicated
the mono build is the place to perform mozroots


2) MonoDevelop build
  - The following is in their MonoDevelop/main/scripts/configure.sh:

    *DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"  *

  It's bash specific so it fails. Perhaps we should just include this

    *env SHELL=/usr/local/bin/bash*

  in our ports make file?

 - These were my dependancies over and above what I had. I didn't have a
clean instance so there is most likely others. I think these are all
addressed in the ports Makefile:
    cd /usr/ports/textproc/p5-XML-LibXML/ && make install clean
    cd /usr/ports/x11-toolkits/gtk-sharp20/ && make install clean
    cd /usr/ports/x11-toolkits/gnome-sharp20/ && make install clean  -> had
to run REinstall for this one???

   gnome-sharp20 was interesting becuase I had to run a make re-install
after the MonoDevelop build. wierd. Any ideas why?

3) Running

 - As stated above until Kqueuewatcher is fixed, we need to

      *setenv MONO_MANAGED_WATCHER true*

    I put it in my monodevelop run script

 - Are we running an old version of gtk-sharp? When starting monodevelop we
get hundreds of these messages:






*  ERROR [2015-08-20 22:21:29Z]: GLib-Critical: Source ID 1858 was not
found when attempting to remove itStack trace:    at
GLib.Source.g_source_remove(UInt32 )   at GLib.Source.Remove(UInt32 tag)
at GLib.Timeout+TimeoutProxy.Dispose(Boolean disposing)   at
GLib.Timeout+TimeoutProxy.Finalize()*


   There seems to be updated here:


https://github.com/mono/gtk-sharp/commit/7ea0c4afaf405df2dfc5a42e098e9023ecc1c51c

    PC-BSD just updated itself so I'll see if packages is already updated

  - MonoDevelop thinks it's running on Linux. This is the output when it
starts:



*    mono /usr/local/lib/monodevelop/bin/MonoDevelop.exe --no-redirect
INFO [2015-08-10 22:29:49Z]: Starting MonoDevelop 5.10    INFO [2015-08-10
22:29:49Z]: Running on Mono 4.0.1 (tarball Tue Aug  4 06:03:31 UTC 2015)
(64-bit)*
***************************************************************
*    INFO [2015-08-10 22:29:49Z]: Operating System: Linux*
****************************************************************






*    FreeBSD Prescott 10.1-RELEASE-p26 FreeBSD 10.1-RELEASE-p26 #0: Tue Jul
28 22:55:17 UTC 2015
root@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys/GENERIC  amd64    INFO
[2015-08-10 22:29:49Z]: Using GTK+ 2.24.27    INFO [2015-08-10 22:29:49Z]:
Add-in loaded: MonoDevelop.Core    INFO [2015-08-10 22:29:49Z]: Add-in
loaded: MonoDevelop.Ide    WARNING [2015-08-10 22:29:49Z]: No proxy
credential provider was found    INFO [2015-08-10 22:29:49Z]: Initializing
Runtime Mono 4.0.1    Starting MonoDevelop*

  Booo! where do I change that???

I think that's it? 5.10 isn't released yet so if we jump on this now, we
could be current at least for a little bit?

What is the etiquette for updating the Mono and MonoDevelop ports? It would
be nice if I could leave this to someone that knew what they were doing,
but I am willing to take it on if needs be. I would be willing to support a
3 month port update cycle for one year.


Thanks,

Russ



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABx9NuQGnE7o3xRFYe62WSMmNQQMPm=s6Oajmhw1-JDb0ib=_Q>