Related to the "Not finding libraries" - But within a workspace with a static lib not finding project headers in a framework.
Related to the "Not finding libraries" - But within a workspace with a static lib not finding project headers in a framework.
- Subject: Related to the "Not finding libraries" - But within a workspace with a static lib not finding project headers in a framework.
- From: Alex Zavatone <email@hidden>
- Date: Thu, 29 Dec 2016 16:26:25 -0600
I've got a similar problem to Howard's, but (as in the title) with an iOS app within a workspace where its static lib can't see project headers from a framework that is also within the workspace.
This works perfectly in another workspace from an iOS app target which is linked to the FW.
I have the FW's header set to be public, and this it imports one project level header within <> that then imports 1 project level header which then imports 4 project level header that are in different directories.
Now, I know I can move those headers to be public, but that's simply wrong and it exposes our data model.
Before I added this project with the static libs and the project that makes my FW to the workspace, I would manually copy the FW into a location where the static lib would see it, and this framework was linked to the static lib From Build Phases, Link Binary with Libraries. If I open the project that only builds the static lib that links to the FW, it builds without a complaint. All search paths are the same.
Is there a different practice that is required to locate framework headers from within a static lib?
Thanks in advance.
Alex Zavatone
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden