Lists

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

Statically linking *Obj-C* lib

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

Statically linking Obj-C lib

Subject: Statically linking *Obj-C* lib
From: Steven Kramer <email@hidden>
Date: Wed, 9 Feb 2005 12:31:12 +0100


Hi all,

Is there an (easy) way to link in Obj-C classes and categories from a *static* library that have no direct dependencies in the application? The problem is that classes from the library that are referenced only indirectly (e.g., in a NIB file) are not linked in. I might be able to solve this with a lot of export directives, but that's really not the way to go.

IIRC ld links at module level, so I might be able to force a dependency on each .mm file by including a (C++) global with initializer or something like that. But I'm sure there must be an even easier way than that... right?


Regards,

Steven Kramer

--
email@hidden
http://sprintteam.com/

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: Statically linking *Obj-C* lib
From: Jared Watts <email@hidden>


Prev by Date:
Serious crash from setNeedsDisplayInRect:

Next by Date:
Re: WTF, my application is writing *directly* into Xcode log?

Previous by thread:
Re: Serious crash from setNeedsDisplayInRect:

Next by thread:
Re: Statically linking *Obj-C* lib

Index(es):

Date
Thread