On Jun 16, 2015, at 01:36 , Kevin Meaney <k...@yvs.eu.com> wrote: > > #if os(iOS)
Ah, thanks for reminding me about that. I keep forgetting that Swift has a form of #if. On Jun 16, 2015, at 03:22 , Maxthon Chan <m...@maxchan.info> wrote: > > You actually can build the OS X and iOS versions of the same framework with > the same name, just keep the targets in separate projects and double-check > when linking. That’s a good approach, but I’ll have to experiment to find out how usable it is in this case. Managing separate projects means managing separate repositories (or manually forcing Xcode to stuff multiple projects in a single repository). It’s also a bit more complicated than I said, because there are 4 targets (iOS, Mac MAS, Mac non-MAS and a data test app) and I want to use 3 different namespaces for access control. It starts to get a bit hard to manage. What I’m actually thinking of doing is finishing the conversion using a single target, then jettisoning the framework structure and just building all the source files together. There was no real reason for the frameworks other than access control, and (in this case) there’s no real reason for the access control once the code is written. _______________________________________________ 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
