Using macports dylibs without macports

[Jim Busser]

On 2009-09-17, at 3:15 PM, Travis Griggs wrote:

> Static linking isn't an option for us. And your point about it being  
> major version specific is not really doable for us. So I'll do some  
> more digging in how to get Cairo built for myself to run on multiple  
> version and be able to be placed in the our .app (which I don't  
> myself build).
>
> Just for PoC type of thing, I did try the tool referenced, and it  
> blew up:
>
> ImportError: No module named modulegraph.util
>
> I'm not sure it would even work for this anyway. The .app of  
> interest is a Virtual Machine engine for VisualWorks Smalltalk. So  
> the .app doesn't itself need the Cairo libraries. But one can write  
> a Smalltalk app that wants to load and use Cairo dlls.

Isn't Apple's own Xcode supposed to enable *some* of what MacPorts is  
less well positioned to do?

Is the issue that Xcode could provide some, but not all, of what would  
be needed?