Re: Proper way to set up constants when building an iOS framework
Re: Proper way to set up constants when building an iOS framework
- Subject: Re: Proper way to set up constants when building an iOS framework
- From: Charles Jenkins <email@hidden>
- Date: Tue, 12 Apr 2016 12:43:56 -0400
I imagine you’re already doing this, but your message wasn’t clear, so forgive me if I sound patronizing.
The constants should be declared extern in the header file, but not assigned any values. The value assignments should appear inside a single .m file in your framework.
--
Charles
On April 12, 2016 at 12:35:55, Alex Zavatone (email@hidden) wrote:
Do you guys have any tips on setting up a constants file when building a framework?
I just moved in our SecurityConstants.h and KeychainWrapper, went to build my framework and now it's full of duplicate symbol build errors in the .o files.
All the constants are NSString * const and defined in a .h file, which is is included where needed.
Are there special approaches that I need to take when working with a framework on iOS that don't cause issues within a standalone app that would prevent this?
Thanks in advance.
Alex Zavatone
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden