Categories in tests

[MSch]

Seems that linking against a static library doesn't load the Categories?

Can someone try the tests in master vs. the tests in framework-target?

Maybe there's another explanation.

[steipete]

Yes, unless you use -all_load categories w/o classes are not loaded in static libs. There are workarounds though.

[steipete]

I have nothing against -all_load, but putting and empty class in categories would fix it too

From Nimbus (who copied it from three20)

/**

• Force a category to be loaded when an app starts up. *
• Add this macro before each category implementation, so we don't have to use
• -all_load or -force_load to load object files from static libraries that only contain
• categories and no classes.
• See http://developer.apple.com/library/mac/#qa/qa2006/qa1490.html for more info. */

  define NI_FIX_CATEGORY_BUG(name) @interface NI_FIX_CATEGORYBUG##name @end \

  @implementation NI_FIX_CATEGORYBUG##name @end

[steipete]

But I guess you won't like it, as it's again macro magic ;)

[myell0w]

you need to add all_load linker flag

sent from phone

Am 10.07.2011 um 11:12 schrieb MSchreply@reply.github.com:

Seems that linking against a static library doesn't load the Categories?

Can someone try the tests in master vs. the tests in framework-target?

Maybe there's another explanation.

Reply to this email directly or view it on GitHub: https://github.com/foundationkit/FoundationKit/issues/24

[MSch]

I'm all for the macro magic. Way better than forcing our users to change build settings.