Aha! Awesome. That will work nicely.
Now my concern is the compiled c lib that my code links to. Do I also have to rebuild that with non ARC flags too? Sent from my iPhone > On Feb 23, 2016, at 6:33 PM, Greg Parker <gpar...@apple.com> wrote: > > >> On Feb 23, 2016, at 3:25 PM, Alex Zavatone <z...@mac.com> wrote: >> >> Would it be recommended to package my ARC code with ARC turned off and >> package that in a framework and then link to that from the non ARC app that >> will need to load it? > > Building a separate dylib or static archive is not necessary, but it might be > the simplest way to get the project settings correct. Writing custom build > flags for each of your source files is likely to be error-prone. > > You can add a check to your ARC source files that will cause a compiler error > if ARC is mistakenly off: > > #if !__has_feature(objc_arc) > # error This file must be compiled with ARC enabled. > #endif > > > -- > Greg Parker gpar...@apple.com Runtime Wrangler > > _______________________________________________ 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
