OK. Immediately dead in the water. If I create a brand new workspace and then create a brand new iOS target framework and include it in to that workspace, then drag into the workspace a project that outputs (pjsip-ios) a .a file (pjsip-ios), the workspace does not contain the build scheme for the project I just dragged in.
The project that I just dragged in DOES have a build scheme that works to build a .a file. If I close it from the workspace, and open up the project by itself, I can see it. On Mar 10, 2016, at 1:21 PM, Jens Alfke wrote: > >> On Mar 10, 2016, at 9:47 AM, Alex Zavatone <z...@mac.com> wrote: >> >> In Xcode 7.x, if I have an app target that links to a framework (and that >> framework is added to the app as a dependency) and that framework also has a >> library that is added to the framework AND is also is added to the framework >> as a dependency, would we expect that when A is built, it will link to and >> include B and B will link to and include C? > > Are you talking about static or dynamic linking? > > But yeah, what you’re describing sounds like business as usual for either ld > (if it’s static) or dyld (if it’s dynamic.) > > —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
