Using macports dylibs without macports

Paul Dennis Simonson psimonso at illinois.edu
Mon Sep 28 15:36:13 PDT 2009


Here is some example output from Terminal:

Last login: Mon Sep 28 17:32:39 on ttys000
DYN-130-126-15-92:~ paulsimonson$ /Volumes/SIMONSON/ShrimpAnalysis_SL
; exit;
dyld: Library not loaded: /opt/local/lib/libfreeimage.3.dylib
  Referenced from: /Volumes/SIMONSON/ShrimpAnalysis_SL
  Reason: no suitable image found.  Did find:
	/opt/local/lib/libfreeimage.3.dylib: mach-o, but wrong architecture
Trace/BPT trap
logout

[Process completed]


On Sep 28, 2009, at 5:23 PM, 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.  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.
>>
>>
>>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users



More information about the macports-users mailing list