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

[Michael Hutchinson]

On Fri, Jan 29, 2010 at 11:31 AM, JoelMarcey <jimarcey at gmail.com> wrote:
>
>
> Michael Hutchinson wrote:
>>
>> I suggest you edit the file
>> /Library/Frameworks/Mono.framework/Versions/2.6.1/bin/glib-gettextize,
>> find the line that says
>> prefix=/tmp/install
>> and change it to
>> prefix=/Library/Frameworks/Mono.framework/Versions/2.6.1
>>
>> Also please file a bug against the Mono Mac packaging.
>>
>>
>
> I made that change and progressed a bit (I will file the bug). But now a new
> can of worms has opened when running autogen.sh.
>
> I guess before I go about trying to debug this build process, here are some
> questions:
>
> 1. Can mono-tools, specifically gui-compare, actually be built on Mac OS X
> successfully using the packaged install of Mono for the Mac.

Doesn't look like it. I tried on my machine but r

> 2. Am I going about it the right way, via autogen.sh?

That's the correct way to build from SVN, yes. Release tarballs have
been pre-autogenned, so you don't need autotools, and can just run
configure directly.

> 3. If (1) and (2) are answered yes, how should approach debugging the build
> process. See attached output file after running autogen.sh?
>
> http://old.nabble.com/file/p27374503/MonoToolsBuild.rtf MonoToolsBuild.rtf

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.

-- 
Michael Hutchinson
http://mjhutchinson.com