Hi after I've updated my mac to OS X 10.10(Yosemite) my project won't compile now. :(
I've tried to delete derivedata but still the problem occurs.
Here's the error
/Users/ronpelayo/loke/Boogiespot-iOS-Library/BoogieLibrary/BoogieSpot.xcdatamodeld: Compilation failed for data model at path '/Users/ronpelayo/Library/Developer/Xcode/DerivedData/BoogieLibrary-ddzzhhrbirmakmgvaskpalwekowx/Build/Products/Debug-iphoneos/BoogieSpot.momd/BoogieSpot 10.mom'
and here's the screenshot of my xcdatamodeId
I hope someone can help me with my problem I don't know what to do now :(
It appears that the problem is within OS X 10.10(Yosemite)
http://openradar.appspot.com/radar?id=6385584100605952
I've tried to compile my project in Xcode 6.1 and it's running now but I'm still investiging if it has bugs.
Related
Lately I've started to take up a course for learning swift to devolp iOS OS X and Watch OS apps. I'm taking this course on udacity. The first step is to download a project and put it in a folder on your desktop. I had to open the app and then run it, which should've worked. But not for me somehow. I hit run and the following error showed up (this is the complete error log):
Some poeple suggested that I should update my XCode but I already have. I currently have XCode 7.3! I'm quite new to this platform, that's also why I'm doing this course, so I don't really know what I have to do. Can someone please tell me what's going on here?
This is the result of a corrupted swift class. If you encounter a class looking similar to the following code:
Ôæ≠fiÔæ≠fiqcaJÔæ≠fihJ0ç硡ˇ2ç硡ˇ$5y$ġˇˇ% 7.ġˇˇÔæ≠fiÔæ≠fiP‚—ġˇˇfl‚ġˇˇ ˗ġˇˇ∞B‚ġˇˇÄ+€
Try to re-create the class or re-download it. This solved my problem and to me, it would look like the only solution possible for a corrupted class.
Delete derived data.
Windows->Projects->select your project and delete derived data
This worked for me for couple of projects which i downloaded from internet.
I do everything restarts Xcode, rebuild Project, adding toolChains lock unlock them,
so there are two possibilities
first, maybe you install the beta version of Xcode
or try this, this work for me->
I tried to run a project in Xcode12/Swift4, while the project was written on Xcode8/Swift3
so I install Xcode version 11.7 and run this work for me.
if you not done with 11.7 then install another version of Xcode and try the appreciated version
May this help you
Recently I am working on my new project on Xcode 6 with cocos2d-x 3.6
I created the cocos2d-x project using Terminal and I followed the steps of the tutorials below:
https://www.youtube.com/watch?v=qXqgSNUf9Cc
Obviously, the tutorial is not using Xcode 6.
Sorry for the screen capture because I can't explain the error
http://goo.gl/iyF3uC
My iMac is OS X Yosemite.
Please help me to fix my errors
Thanks.
Matthew
Looks like it is just warning, not error. You can avoid the warning by renaming variables passed as argument, like
Point(double x_, double y_) : x{x_}, y{y_} {}
I updated my Flash Builder SDK to use the latest AirSDK 15,change the application to use 15.
After that I got the error: Could not resolve
<s:ViewNavigatorApplication>
I the found some one else had that problem and added the /frameworks/libs/mobile to the build path I added the path and then i got a different error: Could not resolve
<s:Callresponder>
I then tried to add the MX path and a lot of other paths but could not get rid of the error. I have now spend over 10 hours all because I need to update my iOS application so it will run on the new iOS8.
Flash Builder 4.6 Premium - Mac OS Maverick.
Thanks.
Adding
-swf-version=26
--namespace+=http://ns.adobe.com/mxml/2009,${flexlib}/mxml-2009-manifest.xml
--namespace+=http://www.adobe.com/2006/mxml,${flexlib}/mxml-manifest.xml
--namespace+=library://ns.adobe.com/flex/spark,${flexlib}/spark-manifest.xml
to the "Additional compiler arguments" in properties -> Flex Compiler seems to fix it.
My project was working without errors on XCode 4.2 on Lion. Now I'm running Mountain Lion with XCode 4.4 and when I try to build the project it gives me an error that tree.h file cannot be found. I checked the header search path and it was correct. I searched the web for such an error and found the same solution on many different pages but couldn't understand that particular solution, see for example this page.
How can I solve this problem? Alternately, can you clarify the weird solution that is spread all over the internet?
I had to add another header search path which is: $(SDKROOT)/usr/include/libxml2. This fixed the problem.
Go in the XCode preferences and install the command line tools.
UPDATE: QUESTION CLOSED: Fixed myself with a little backtracking. I'm using a framework that requires a source tree variable. (Sparrow). I updated the source tree on my main Mac Mini but not in my MacBook Pro. So, Xcode was searching an old directory due to that mistake.
This may be one of those weird Xcode bugs, so I'm looking for a little advice. I have Xcode 4.3.2 (latest as of this writing Apr 7 2012) installed on two Macs. I have a project saved in Dropbox so I can quickly get at it and work on it from either place. I've done this with several other projects and never experienced this issue.
One one computer, a Mac Mini, the project builds fine. On the other, a 2009 MacBook Pro, I get build errors. For one, even though I'm using -fno-objc-arc on a few of the source files, I am still getting ARC related errors. That is very puzzling to me. No issue when building on the Mac Mini. I'm also getting "file not found" errors pertaining to the .pch file. The error log is pointing me to a strange path like
/var/folders/9l/s_phv6yj0hv6q82_lrdcckb00000gn/C/com.apple.Xcode.501/SharedPrecompiledHeaders/...Prefix.pch' file not found
Here's what I've tried so far
Deleted Xcode and reinstalled from the MAS
Deleted the /var/folders directory called out in the logs
Removed the project build directory
Performed a Product -> Clean in Xcode
Restarted Xcode numerous times
Still no dice. Looks like unless I can nail down this issue, I'll be stuck working from one workstation for this project only. All other projects work fine when doing this.
Thank you for any help you can offer.
I was using a Source Tree variable in XCode, and one of the variables was out of date and pointing to the wrong path. One of the source files that was subsequently updated was working on one Mac but throwing errors on the other, which caused the build to fail and the linker to display strange errors.