[MonoDevelop] MonoDevelop on OSX filters assembly list

Michael Hutchinson m.j.hutchinson at gmail.com
Thu Jan 15 18:53:09 EST 2009


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.

-- 
Michael Hutchinson
http://mjhutchinson.com


More information about the Monodevelop-list mailing list