[Mono-osx] Build 'mono-tools' on Mac OS X with Mono 2.6.1

[Michael Hutchinson]

On Sat, Jan 30, 2010 at 2:09 PM, JoelMarcey <jimarcey at gmail.com> wrote:
>
>
> Michael Hutchinson wrote:
>>
>>
>> The first issue is that autotools is not finding the pkg.m4 macro, and
>> the mono-tools autogen.sh does not respect $ACLOCAL_FLAGS. After this,
>> however, I ran into a gnome-sharp dependency, which certainly won't
>> work on Mac. So even after fixing glib-gettextize and ACLOCAL_FLAGS,
>> you'll have to hack the configure.in and Makefile.am, maybe add flags
>> to disable the things that depend on Gnome#.
>>
>> BTW please use plain text for attachments, not rtf.
>>
>
> So, if I can summarize:
>
> 1. Don't even try building mono-tools on a Mac against the packaged version
> of Mono (.dmg)

Right, unless you can alter the mono-tools makefiles to eliminate the
linux-only Gnome# dependency or make it optional.

> 2. It will be hell to try to build mono-tools on a Mac even if you built
> Mono from source.

It wouldn't make any difference. The issue is Gnome#, not the dmg.

> 3. Building/running this on Windows would be a non-starter.

Probably, cygwin is painful enough and you'd still have the Gnome# problem.

> So my bottom line in order to get mono-tools (specifically gui-compare)
> running is to use Linux, and probably in my case since I only have Mac and
> Windows machines, I should just use the Virtual PC or VMWare downloads of
> Mono and try to build mono-tools from there.
>
> Would you agree? Any other, more efficient ideas?

A few other options:
a) You could open the Linux rpm archives (I know that e.g. 7-zip on
Windows can do this) and extract the binaries.
b) Some parts of mono-tools might be buildable separately. For
example, gui-compare has a mdp project file (MonoDevelop 1.0 format,
but MD 2.2 can handle it).
c) You could fix the mono-tools makefiles to make the GNOM# dependency
optional, so the problem is permanently fixed.

-- 
Michael Hutchinson
http://mjhutchinson.com