[libdispatch-dev] Excluding libdispatch from being linked into executable
Kevin Van Vechten
kvv at apple.com
Thu Jan 13 10:53:17 PST 2011
On Mac OS X, libdispatch is part of libSystem.B.dylib along with many other default system components. The thread you're referring to does not get created unless lib dispatch is actually used. In your case, it's probably being used indirectly by a higher level framework used by your application such as CoreFoundation, Foundation or AppKit.
On Jan 13, 2011, at 10:50 AM, Stefan Marr wrote:
> Hope this is the right place to ask for advice.
> I am using Xcode 3.2 and am a bit annoyed by the fact that GCP gets automatically included in my binary.
> It does not seem actually to cause any problems, but it is annoying when I debug my multithreaded code, since there are always additional thread that do not have any reason to exist.
> Is there any way to tell Xcode to not include libdispatch?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libdispatch-dev