Re: Not finding @import module
Re: Not finding @import module
- Subject: Re: Not finding @import module
- From: Steve Mills <email@hidden>
- Date: Sun, 07 May 2017 00:46:44 -0500
On May 6, 2017, at 01:00:38, Steve Mills <email@hidden> wrote:
>
> One my work machine running 10.10.5 and Xcode 7.2.1, I added a subproject that builds an iOS framework (UnrarKit) to my iOS app project. The one source file in the app project that needs it got an @import added and it was found. I checked everything in and synced on my home machine running 10.12.4 and Xcode 8.3.2, but building gets an error that it can't find UnrarKit. One difference between the two is that the older system builds the UnrarKit.framework in the standard DerivedData folder, but the newer one builds it in the "build" folder next to the .xcodeproj. Could that be causing the problem?
>
> The UnrarKit framework target was added as a dependency in the app target, and it links to it. I also tried changing the @import to a good ol' #import "UnrarKit/UnrarKit.h", but that also fails to find it.
Found the difference and the problem. My home machine had Prefs->Locations->Derived Data->Advanced set to Legacy, where the work machine had it set to Unique (the default). I'm pretty sure we needed to change that a long time ago to keep build folders in more logical places than the stupid DerivedData folder. I changed the home machine to Unique, cleaned and built, and it build with no problem. Although the error still showed up in the file that was trying to @import or #import. Had to quit Xcode and relaunch to make that go away.
--
Steve Mills
Drummer, Mac geek
_______________________________________________
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