• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Another Xcode update, another failure to build.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another Xcode update, another failure to build.


  • Subject: Re: Another Xcode update, another failure to build.
  • From: sqwarqDev <email@hidden>
  • Date: Thu, 13 Aug 2015 16:58:17 +0700


> On 13 Aug 2015, at 11:37, Graham Cox <email@hidden> wrote:
> But the linker fails to find the framework:
>
> ld: warning: directory not found for option '-F"/Users/grahamcox/Projects/Mapdiva Projects/Artboard/../../Library/Developer/Xcode/DerivedData/Drawkit-gzweppsofrkdiyasaleyeleblyor/Build/Products/Debug”'

This may be voodoo magic or just good luck, but…

I was having the same problem a couple of weeks back after reverting to an earlier version of the Sparkle framework to one I’d previously embedded. I cleaned out the original, embedded the regression and thought I’d be away. Alas, Xcode kept looking for it. Cleaning out the DerivedData’s didn’t help. Something kept telling it to go looking in that DerivedData folder on every clean build.

I eventually hit on the theory that there must be a property list somewhere telling Xcode where to look. Perhaps deleting my app’s plist and restarting would have worked, but I eventually did all the clean outs in Xcode, including deleting the framework, linker paths, clean builds etc,  and then in Terminal did

defaults delete -app AppName

(note: AppName is case-sensitive, but is not the bundle identifier. e.g.. defaults delete -app TextEdit will do it.)

After that I re-added the framework and the linker path etc and the problem was solved.

Note of caution: also check in the Finder that your framework is not lurking about in more than one place in your project’s root or anywhere else. After I did the above, I started having similar problems to those Alex was reporting last week with Xcode and source control (i.e. Xcode wouldn’t let me commit, but kept telling me there were commits to be had), which were down to a forgotten copy of the Sparkle framework that didn’t show up in Xcode’s project navigator, but was still stuck in my project’s root folder.


Best


Phil


BatteryAlert - keep track of your Magic Mouse, Keyboard and Trackpad. More info on sqwarq.com/batteryalert
OSXClock - big, beautiful alarm clock and timer for your mac. More info on sqwarq.com/osxclock

http://applehelpwriter.com
http://sqwarq.com - apps for OS X & iOS












_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


References: 
 >Another Xcode update, another failure to build. (From: Graham Cox <email@hidden>)

  • Prev by Date: Another Xcode update, another failure to build.
  • Next by Date: Re: Mavericks vs Yosemite line spacing
  • Previous by thread: Another Xcode update, another failure to build.
  • Next by thread: What version of OpenGL bundled in El Capitan?
  • Index(es):
    • Date
    • Thread