NSString crash?

[Mike Hess]

I've been building a library for my iPhone applications, and have been expanding upon apple's NSString class.  I have an interface of @interface NSString(NSString_Expanded), and a similar such @implementation.  My issue is that many functions, when compiled in Library form, crash with a "does not respond to selector" error. The implementation file containing that function definitely has the Library as a target, so I am confused as to why this could possibly be happening (The Library also has the application as its target).  Interestingly enough, when I drag the implementation file to the project, the crash stops happening, but I really would prefer not to copy it over every single time.  Also many features of the library work perfectly so I'm guessing it is something NSString specific (Or has to do with the fact the NSString is toll-free bridged.)  Any ideas? Thanks for any help! Mike

[Adam Martin]

You're not forgetting the -ObjC flag, are you?

And if you're using 3.0, also the -all_load flag, to work around the temporary SDK bug?

(both in "other linker flags")

--

Weird typos? Sorry, this mail was written on an iPhone :)

[Mike]

Thanks for the quick response! That was it.

Mike