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 (z...@mac.com) 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/cejwork%40gmail.com This email sent to cejw...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
