Re: Project and header searchpaths for iOS in a workspace
Re: Project and header searchpaths for iOS in a workspace
- Subject: Re: Project and header searchpaths for iOS in a workspace
- From: "Dr. Michael Lauer" <email@hidden>
- Date: Fri, 12 May 2017 13:32:28 +0200
> I’m in an interesting search path mess where I’ve reconstructed this app several times and it’s a workspace that contains 6 projects and links to a framework target output from another workspace.
>
> Suddenly, even though the app builds, on one of the 3 Macs I have rebuilt and relinked this workspace on, one of the sub projects can’t see all other projects within the workspace.
>
> But the app builds just fine, it’s just that I get endless “This file.h not found” while working in the project.
>
> Besides the endless digging through build settings and Header Search Paths (which I’ve done), is there a way to output what the app or current Xcode dev environment thinks the resolved values for the header search paths currently are?
I don’t have a direct answer for you, however for more complex projects
(e.g. an iOS app with a multiple extensions, a watchOS target, a tvOS target, all employing different
builds of the (same) custom frameworks etc.) I had endless build problems until I
a) stopped using workspaces with their automatic dependency resolution and reverted to using project files with subprojects,
b) unchecked all ‚find implicit dependencies‘ in all schemes I had, and
c) made sure that my explicit dependencies were complete and correct.
Once I did this, everything built nicely.
Cheers,
:M:
_______________________________________________
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