[cairo] Universal Framework for Mac OS X

[Neil Mayhew]

On 22/03/09 05:43 PM Andreas Krinke wrote:
> I wanted to embed everything in my app bundle. Using this framework 
> there is no need to distribute anything else.

I had assumed you were talking about a system-wide framework, eg in 
/Library/Frameworks, which I don't think offers a great deal over a 
MacPorts library. However, maybe there are aspects to this that I 
haven't understood.

I know it's something that Apple recommends, but with libraries that are 
likely to be used by other applications it seems to me like such a waste 
for each app to have its own private copy.


On 22/03/09 05:33 PM Ryan Schmidt wrote:
> ... on Mac OS X you really want to distribute something that is 
> relocatable...

I'm not sure I understand why this is particularly important, unless you 
want to put the framework inside your app.

> And you don't really want to distribute things that install into 
> /opt/local, because that would overwrite and interfere with anything 
> the user had themselves installed with MacPorts.

One solution would be to check in the installer whether /opt/local is 
already there and put up a message to the user telling them which ports 
they need to install to support the app, and not install the ones from 
the installer. Or the installer could offer to run MacPorts to install 
what's needed. This would be unusual behaviour for an installer, but I 
would think that very few end-users actually use MacPorts, and those 
that do would presumably be comfortable with it.

Good points, both. Thanks for explaining things.

--Neil