> Le 13 déc. 2016 à 21:59, Alex Zavatone <z...@mac.com> a écrit : > > I've got a lovely (cough) non ARC iOS project that consists of 1 project file > that the target app is made from that links to 5 other projects that are > compiled to static libs through the odd method of specifying their path in > Other Linker Flags. > > This is built (cough) through the legacy build path setting of having the > build folder within each of the project folders. The absolute path of each > is what is entered in Other Linker Flags of the main project file to allow > the iOS target app to link to these static libs. > > Yes, it hurts my brain too. > > Both the project file and one of the static libs need to be aware of my > framework. > > Considering how much of a mess this whole thing is to figure out, I simply > paste one copy of my framework into Framework folder of the app and the > Resources folder of the static lib that needs it, so which ever one Xcode > picks doesn't matter. > > This is sloppy as hell. > > Is there a method that uses a shortcut, alias or symbolic link to have the > framework that should be in the Resources folder then the static lib ids > built refer to the actual file that is in the Frameworks folder that the app > uses?? > > How do people handle this > 1 lib in a project needs to refer to another > compiled lib? >
Why do the static lib need the framework ? A static lib is just a bundle of .o file packed into a single file. There is no linking step involved. So you need just the header of the framework, not the framework itself. Only the final binary need the framework. _______________________________________________ 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
