Using macports dylibs without macports

[Jochen Küpper]

On 29.09.2009, at 00:23, Paul Dennis Simonson wrote:

> All of the *.a files build just fine using MacPorts.  I build and  
> link my programs using XCode 3.2, and the build is successful when I  
> build a command line utility and link to the *.a files.

Apparently you do not link in the .a archives, but against the .dylib  
dynamic libraries.
What does
    otool -L <utility>
say?

> However, the program is looking for the *.dylib files when I try to  
> run the program on another computer and of course fails to find them!
>
>
> On Sep 28, 2009, at 1:56 PM, Ryan Schmidt wrote:
>
>>
>> On Sep 28, 2009, at 12:27, Paul Dennis Simonson wrote:
>>
>>> Is there any way to force MacPorts to make a static library that  
>>> we can link to and distribute easily?  It used to do this!!!
>>
>> Ports should install static and dynamic libraries wherever  
>> possible. If you find ports that are missing one or the other,  
>> please file tickets for those ports.

/Jochen