[MonoDevelop] MonoDevelop on OSX filters assembly list

[David Eliott]

Alright, so what I've done is opened the .app and opened the script from
inside. The following is at the top of the script file:

### SYNCH BLOCK: any changes to this block should be kept in sync with the
one in Makefile.include and mdtool.in
MD_PKG_CONFIG_PATH=$APP_PATH/Contents/MacOS/lib/pkgconfig:/tmp/build_deps/li
b/pkgconfig/:/usr/lib/pkgconfig/:/usr/local/lib/pkgconfig/:/usr/share/pkgcon
fig/:/usr/local/share/pkgconfig/
if test -d /usr/lib64; then
MD_PKG_CONFIG_PATH=$MD_PKG_CONFIG_PATH:/usr/lib64/pkgconfig/:/usr/local/lib6
4/pkgconfig/; fi
### END BLOCK

if [ -n $PKG_CONFIG_PATH ]; then
    export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$MD_PKG_CONFIG_PATH
else
    export PKG_CONFIG_PATH=$MD_PKG_CONFIG_PATH
Fi

So in the paths above we have:

$APP_PATH/Contents/MacOS/lib/pkgconfig
/tmp/build_deps/lib/pkgconfig/
/usr/lib/pkgconfig/
/usr/local/lib/pkgconfig/
/usr/share/pkgconfig/
/usr/local/share/pkgconfig/

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.

Thanks for your help Michael!

Draek



On 15/01/09 4:53 PM, "Michael Hutchinson" <m.j.hutchinson at gmail.com> wrote:

> On Thu, Jan 15, 2009 at 6:32 PM, David Eliott <draekz at gmail.com> wrote:
>> So then what path does the pkg-config tool use when I run the command:
>> 
>>> pkg-config --list-all
>> 
>> And I see all the libraries that I SHOULD have. They are all listed.
>> 
>> I do not believe that those environment variables are present at all in OSX,
>> when I echo $PKG_CONFIG_PATH, there is nothing.
> 
> PKG_CONFIG_PATH isn't set in a normal environment. pkg-config uses the
> prefix that it was built for, which is hardcoded into it at build
> time, and there's no way for us to extract that short of disassembling
> the pkg-config binary.
> 
> For (major) performance reasons we don't use pkg-config itself, but
> instead look through all the .pc files directly, so we have to
> determine the paths in the launch script. Clearly the Mac MD launch
> script is not doing that correctly, but as I explained, the workaround
> is trivial.
> 
> I don't know what launch script the Mac installer uses, but we on the
> MD team don't maintain it.