[Mono-bugs] [Bug 349195] Embedding Mono broken on OS X: problematic references

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Dec 18 05:56:20 EST 2007


User andreas.faerber at web.de added comment

--- Comment #3 from Andreas Färber <andreas.faerber at web.de>  2007-12-18 03:56:19 MST ---
The provided Mono.framework package installs to /Library and should thus be
designed to work there.

If someone wants to use Mono in a non-standard location they can easily use
install_name_tool (e.g. in a Run Script action in Xcode) to overwrite the
locations in their private Mono. The imeem guys have been telling this on the
Mono-osx list multiple times for Dumbarton, and this change was not discussed

Embedding Mono, I have to use install_name_tool for my application as well to
replace /Library/Frameworks/Mono.framework/Versions/xxx/lib/libmono.0.dylib
with something more compatible like /Library/Frameworks/Mono.framework/Mono, so
this is nothing out-of-the-world.

However asking regular users to (install and) use this tool for Mono.framework
just because some developer wants to ship Mono inside their application bundle
instead of where the package installs to is really out of the question.

Btw if someone wants to embed Mono in their application bundle then
Contents/PrivateFrameworks/Mono.framework/ is the place to do it, not
Contents/(bin|lib|...), the current path is therefore still unsuited and would
need to be changed by someone embedding it correctly as well.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list