[MonoDevelop] MonoDevelop on OSX filters assembly list

[Michael Hutchinson]

On Thu, Jan 15, 2009 at 7:32 PM, Sandy Armstrong
<sanfordarmstrong at gmail.com> wrote:
> On 01/15/2009 04:11 PM, David Eliott wrote:
>>
>> I went through all those paths and it does NOT point to the libraries that
>> the mono installer put in. So what I did was add the path:
>>
>> /Library/Frameworks/Mono.framework/Libraries/pkgconfig
>>
>> Into the MD_PKG_CONFIG_PATH and this allowed MD to see all the libraries.
>> I've talked to some people that work for Novell about it. We'll see how
>> this
>> can be resolved in the installer hopefully.
>
> If there is already a bug filed for this problem, could you add a comment
> with your fix?  If not, could you file one?  It's easy to forget these
> problems if there's not a bug filed...

That looks like an old version of the Linux MD launch script, so maybe
the Mac doesn't use a different script. Perhaps it's just that the
Linux-centric defaults didn't work on Mac.

Back in November I altered the MD launch script to make it relocatable
on Linux, so (among other things) it does

PREFIX="${0%%/monodevelop}/.."
MONO_PREFIX=`which mono`
MONO_PREFIX="${MONO_PREFIX%%/mono}/.."
PKGCONFIG_PREFIX=`which pkg-config`
PKGCONFIG_PREFIX="${PKGCONFIG_PREFIX%%/pkg-config}/.."

MD_PKG_CONFIG_PATH=""
for D in "$PREFIX/.." "$MONO_PREFIX" "$PKGCONFIG_PREFIX" '/usr/local' '/usr'; do
	for PKGDIR in "$D/lib/pkgconfig" "$D/lib64/pkgconfig" "$D/share/pkgconfig"; do
		if [ -d "$PKGDIR" ]; then MD_PKG_CONFIG_PATH="$MD_PKG_CONFIG_PATH:$PKGDIR"; fi
	done
done

I think the change was after alpha 2, but I'm pretty sure this change
would fix the Mac issue. However, I'm not sure if the Mac installer
uses the normal script, or a fork, so this needs to be checked.

-- 
Michael Hutchinson
http://mjhutchinson.com