Here is the information associated with the Linking error statement:
"Linking /User/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development/Cafe.app/Contents/MaxOS/Cafe (97 errors)" --
cd "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe"
/Developer/usr/bin/gcc-4.0 -o "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development/Cafe.app/Contents/MacOS/Cafe" "-L/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development" "-F/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development" -filelist "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Cafe.build/Development/Cafe (Upgraded) 2.build/Objects-normal/i386/Cafe.LinkFileList" -framework Cocoa -arch i386 -prebind -mmacosx-version-min=10.5 -isysroot /Developer/SDKs/MacOSX10.5.sdk
Undefined symbols:
"_vDSP_vqint", referenced from:
_vQuadInterpolate in DSP_vOperations.o
_vQuadInterpolate in DSP_vOperations.o
"_vDSP_vsbsm", referenced from:
_rDerivative in DSP_vOperationsII.o
"_vDSP_vtabi", referenced from:
_rTableLU in DSP_vOperationsII.o
..... (for 94 more)
ld: symbol(s) not found
collect2: ld returned 1 exit status
On Apr 29, 2008, at 12:32 AM, Jean-Daniel Dupas wrote:
Le 29 avr. 08 à 00:32, dct a écrit :
Added info:
The problem appears to be isolated to linking the Accelerate.framework.
The project, which includes a fair number of vDSP calls, compiles successfully (and I can force compile errors by making improper vDSP calls). Obviously the compiler has access to the vecLib.framework via Accelerate.framework.
Unfortunately, once compiled, the project fails to link with the same Linking error statement (97 errors) cited in my first post. It would appear that the linker can't find the framework that was accessed by the compiler (or am I missing something).
These results remain the same whether the Project Setting for "Cross-Develop Using Target SDK:" is set for "Mac OS X 10.5", "Mac OS X 10.4 (Universal)", or "Current Mac OS".
As a check, I built an old, prototype project that was last built about three years ago (and which has no vDSP calls); it built and ran perfectly. I then added one vDSP call (with an #import <Accelerate/Accelerate.h> statement in the appropriate header file). As with my current project it compiled but failed to link.
Initial post:
"My current project fails to build with OSX 10.5.2 and Xcode 3.0 with a Linking error statement:
"Linking/Users/.../MacOS/Cafe (97 errors)
"_vDSP_vquint"' referenced from: ...
"_vDSP_vsbsm"' referenced from: ...
etc (for 97 separate calls) "
Obviously the linker can't find the framework <Accelerate/Accelerate.h>.
This same project builds without error on a MacMini still configured with OSX 10.4.11 & Xcode 2.4.1.
A Spotlight search for "Accelerate.h" reveals three separate paths:
-- /Developer/SDKs/MacOSX10.4u.sdk/.../Accelerate.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../Accelerate.framework/.../Headers
-- /System/Library/Frameworks/Accelerate.framework/.../Headers.
A search for "vecLib.h" reveals four separate paths:
-- /Developer/SDKs/MacOSX10.4u.sdk/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.4u.sdk/.../Accelerate.framework/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../Accelerate.framework/.../vecLib.framework/.../Headers
(I have no idea whether this has anything to do with my problem.)
Any suggestions? I'm stumped and need help."
Yes, posts the linker invocation command line (transcript) instead of just posting the error. We should be able to find what goes wrong from it.