Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

ld linking /usr/local/lib/libxxx.dylib instead of ImageIO/.../lib

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ld linking /usr/local/lib/libxxx.dylib instead of ImageIO/.../lib

Subject: ld linking /usr/local/lib/libxxx.dylib instead of ImageIO/.../lib
From: David Hoerl <email@hidden>
Date: Wed, 2 Jan 2008 14:07:31 -0500

I am playing around with the "Appscript" objective-c script bridge. Using Xcode 3 and the 10.4 SDK, one "ld" fails when the project tries to link my not-universal-library in /usr/local/lib (long story):

Ld /Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript/build/Appscript.build/Release/Appscript.build/Objects-normal/ppc/Appscript normal ppc cd /Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript /Developer/usr/bin/gcc-4.0 -o /Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript/build/Appscript.build/Release/Appscript.build/Objects-normal/ppc/Appscript -L/Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript/build/Release -F/Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript/build/Release -filelist /Volumes/Data/Users/dhoerl/Development/appscript/trunk/src/Appscript/build/Appscript.build/Release/Appscript.build/Objects-normal/ppc/Appscript.LinkFileList -framework Carbon -framework CoreFoundation -framework Foundation -arch ppc -Wl,-single_module -compatibility_version 1 -current_version 1 -install_name /Volumes/Data/Users/dhoerl/Library/Frameworks/Appscript.framework/Versions/A/Appscript -dynamiclib -mmacosx-version-min=10.4 -isysroot /Developer/SDKs/MacOSX10.4u.sdk ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib, file is not of required architecture collect2: ld returned 1 exit status

Now, the question becomes, why did this project want to link with libtiff in the first place? The framework includes the Foundation, CoreFoundation, and Carbon frameworks.

The Appscript provider conjectures that Carbon must reference the ImageIO framework, which has libtiff.dylib (and other such libs) in its tree (./ImageIO.framework/Versions/A/Resources/libTIFF.dylib)

Sooo, the questions becomes - why is the /usr/local/lib/libtiff.dylib getting found before the one inside ImageIO? Is there a workaround on this?

[This also seems to be a potential pothole for someone else, since if the linker DID use it, it might be an incompatible version for ImageIO. Should I enter a bug on this issue???]

David

PS: there are no additional search paths in the project - I did a Edit Active Target and looked. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden Follow-Ups: Re: ld linking /usr/local/lib/libxxx.dylib instead of ImageIO/.../lib From: Thomas Engelmeier <email@hidden> Prev by Date: Re: Link error when building release config of framework Next by Date: Targeting 10.2.8 using Xcode 2.5? Previous by thread: BFD error in Debugger for Xcode 3.0 Next by thread: Re: ld linking /usr/local/lib/libxxx.dylib instead of ImageIO/.../lib Index(es): Date Thread