Re: linking error

2009-06-25 Thread WT
Yes, I just realized that. Silly mistake. Thanks for responding. Wagner On Jun 25, 2009, at 11:44 AM, Alexander Spohr wrote: Each inclusion of your header somewhere creates a new global variable named someString. Change it to have extern NSString* const someString; in SharedDefs.h and NSSt

Re: linking error

2009-06-25 Thread WT
On Jun 25, 2009, at 11:46 AM, WT wrote: On Jun 25, 2009, at 11:38 AM, Dave Keck wrote: The link error is pretty self-explanatory. To solve issues like this, I'd first change the header like so: extern NSString *const someString; and create a SharedDefs.m: NSString *const someString = @"

Re: linking error

2009-06-25 Thread WT
On Jun 25, 2009, at 11:38 AM, Dave Keck wrote: The link error is pretty self-explanatory. To solve issues like this, I'd first change the header like so: extern NSString *const someString; and create a SharedDefs.m: NSString *const someString = @"halla"; This way, any object file can r

Re: linking error

2009-06-25 Thread Alexander Spohr
Each inclusion of your header somewhere creates a new global variable named someString. Change it to have extern NSString* const someString; in SharedDefs.h and NSString* const someString = @"foo"; in SharedDefs.m If you have no SharedDefs.m just crete one ;) atze Am 25.06.2009

Re: linking error

2009-06-25 Thread Dave Keck
The link error is pretty self-explanatory. To solve issues like this, I'd first change the header like so: extern NSString *const someString; and create a SharedDefs.m: NSString *const someString = @"halla"; This way, any object file can reference someString, but only one object file wi