[Mono-osx] Building Mono using Mono.framework [was: Can't type in textbox (2.0 and 3.0)]
Andreas Färber
andreas.faerber at web.de
Fri Jun 20 11:21:40 EDT 2008
Hi,
Am 20.06.2008 um 16:22 schrieb Ockert Labuschagne:
> I have search the list and found the posts you mentioned and it
> might be
> just my lack of experience in non-windows environments, but I could
> not find
> any helpful instructions that I could follow to configure and run a
> working
> build environment. I tried various paths but came short every time.
That's still very vague...
General compilation instructions can be found here:
http://www.mono-project.com/Compiling_Mono
Do you have Xcode 3.0 installed? That should include svn, so that you
can follow these instructions for checking out:
http://www.mono-project.com/AnonSVN
You should end up with two directories, mono and mcs.
To facilitate typing, create a script 'configure-mono.command', as
follows:
#!/bin/sh
export ACLOCAL_FLAGS="-I /Library/Frameworks/Mono.framework/Versions/
Current/share/aclocal"
./autogen.sh --prefix=/Users/you/yournewmono \
PKG_CONFIG_PATH=/Library/Frameworks/Mono.framework/Versions/Current/
lib/pkgconfig
This assumes a standard Mono.framework installation and that you will
be building Mono inside the mono folder.
If you rather want to build in, say, mono-ppc, replace the two "./
autogen.sh ..." lines with "NOCONFIGURE=1 ./autogen.sh" and afterwards
run from your build directory "../mono/configure --
prefix=..." (followed by the usual "make" and "make install").
ACLOCAL_FLAGS is to make sure that the generated configure script can
check for pkg-config presence and doesn't fail due to a syntax error.
PKG_CONFIG_PATH is supposed to pick up .pc files for glib et al.
installed as part of Mono.framework, to avoid configure to fail due to
unresolved dependencies.
Other arguments and variables are documented in "./configure -h" once
generated.
HTH,
Andreas
More information about the Mono-osx
mailing list