Re: Static library confusion
Re: Static library confusion
try
otool -L youapp
At least we will now for sure if it links on the static library or
something else.
I checked this first thing.
otool -L KosmicQuitter
KosmicQuitter:
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
(compatibility version 1.0.0, current version 12.0.0)
/System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
(compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
(compatibility version 1.0.0, current version 168.3.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
(compatibility version 2.0.0, current version 136.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.0.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/
CoreServices (compatibility version 1.0.0, current version 32.0.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current
version 227.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/
CoreFoundation (compatibility version 150.0.0, current version 476.0.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
(compatibility version 45.0.0, current version 949.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/
ApplicationServices (compatibility version 1.0.0, current version
34.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
(compatibility version 300.0.0, current version 677.12.0)
/System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
(compatibility version 1.0.0, current version 185.0.0)
this looks okay to me.
I added the -search_paths_first linker option without effect.
The error begins /Users/Jonathan/Library/Caches/Cleanup At Startup/..
This is created dynamically it seems.
Could the static library write out a bundle for its own use? Seems
strange though could be an anti-tamper measure given the nature of the
library.
The error is, in the end, a GC capability mismatch - so maybe the
static linking is okay and the dynamic(?) bundle is throwing me off
the memory trail.
I will return to examine the apparently working demo.
On 7 Jan 2009, at 15:03, Jean-Daniel Dupas wrote:
Le 7 janv. 09 à 15:12, Sherm Pendley a écrit :
On Jan 7, 2009, at 5:03 AM, email@hidden wrote:
This my problem. I am only linking to the static Library.
That's obviously what you *want* to do, but the error message
you're getting indicates that's not how your app is actually
linked. Disbelieving the evidence is usually not an effective
debugging technique. :-)
When you link with -l, the linker prefers dynamic libraries over
static when both are present. To force static linking, have a look
at:
<http://developer.apple.com/qa/qa2006/qa1393.html>
sherm--
Jonathan Mitchell
Central Conscious Unit
http://www.mugginsoft.com
_______________________________________________
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