A fast, easy to use, free, and community supported 2D game engine
Hello everybody.
I'm using Xcode 3.2.4. and I have updated from rc0 to rc1. I have had some errors when compiling, but now all is working fine. I have followed whole Gryzor instructions (thanks man), but I think that the major problem is the compiler version. Maybe I should have changed the compiler version only, instead of doing all the steps.
Regards.
Moving from rc0 to rc1 using an external project reference, the only change I had to make in the cocos2d source tree was to change the SDK Version back to 4.1.
I'm assuming it's the new SDK, but the "SDKROOT" variable in the cocos2d project changed from "iphoneos4.1" to "iphoneos", which causes all the "cannot find GL/*.h" errors and similar if you're still on the older SDK/Xcode setup.
Mind you, I'm actually slightly past -rc1, so the compiler has already been changed back from llvm.clang.1_0 to llvmgcc422 upstream.
Oh yeah, and I blew away my build/ directory while trying to find the problem. I'm not using a shared build-path either, so my cocos2d build ends up in my project build/ directory.
It'd be nice if Xcode noticed that we had an invalid SDKROOT variable and complained about it, rather than just failing to include anything from it, but at least now I know what to look for.
joekarl
Member
I've been having this issue too.
Using xcode 3.2.4 and sdk 4.1
I've got my project set up with the cocos2d libraries setup as a cross project reference (like @Gryzor).
I can confirm that opening the the cocos2d project and changing the compiler to not LLVM 1.5 makes everything compile.
@jerrodputman To be clear, using rc1 with Xcode 3.2.4 and iOS SDK 4.1, you need to do _both_. imort had already stated he'd changed the compiler.
Post-rc1, the compiler has been changed back to llvmgcc42, but the Base SDK change will stay around, as presumably more and more people move to the 4.2 SDK once 4.2 arrives on hardware in general release (later this month, supposedly)
Yes, I changed back to llvm-gcc since llvm has some bugs specially with blocks and iOS 3.x: it will crash no matter whether you execute blocks or not.
I try to use both compilers just to be sure that cocos2d compiles OK on both platforms, but I leave llvm-gcc as the default one.
The block issue on iOS 3.x can be fixed by weak-linking libSystem.B.dylib, but for LLVM you need to force it with the actual compiler flag. At least for now.
I've updated my code to 0.99.5-rc1 and retina display support is working well now.
I just have one question, Riq: is a Vertical Alignment solution for CCLabelTTF is in the to-do list at all? Horizontal alignment is there, but no Vertical.
I used a modified CCLabel/CCTexture2D classes that implemented Vertical Alignment during 0.99.4, but a lot seems to have changed, and I don't know if copy/paste parts of the code is a good idea.
Thanks.
@sndwav: v0.99.5 uses the same logic regarding CCLabel / CCTexture2D. Some methods were added, some classes were renamed, but if you were using Vertical Alignment in v0.99.4, then should be relatively easy to port it to v0.99.5
There is an open bug with this feature:
http://code.google.com/p/cocos2d-iphone/issues/detail?id=931
For the moment, the priority is bug fixing, so this feature will be added post 1.0
I am using iOS4.2 and Xcode 3.2.5 with cocos2d v0.99.5-rc1 via Cross-Project Referencing.
I am getting ~81 errors similar to the following one:
Undefined symbols:
"_CGAffineTransformRotate", referenced from:
-[CCSprite updateTransform] in libcocos2d.a(CCSprite.o)
-[CCNode nodeToParentTransform] in libcocos2d.a(CCNode.o)
(...)
ld: symbol(s) not found
Can someone help me?
rogerimp
Member
I'm getting a possibly related problem that I haven't seen reported -- or can't find reports of -- here.
In 0.99.5 RC1, iOS SDK 4.2, XCode 3.2.5, writing a project targeted at iPad/iOS 3.2, with Base SDK of iOS 4.2. Project uses the project structure from the XCode templates. The problem is with Code Sense, not compiling. XCode is convinced that I'm writing code for OS X; it won't autocomplete or syntax highlight or jump to any cocos2d/iOS specific features. Instead, it completes OS X specific features. To reiterate, it gives me no complaints on compilation, but it's frustrating to code like this.
When I look at a file with both OSX and iOS code in it, e.g. CCTransition.m line 135-139, it's clear that XCode is touching the code inside the __MAC_OS_X_VERSION_MAX_ALLOWED #ifdef, and not in __IPHONE_OS_VERSION_MAX_ALLOWED.
Any idea how to snap XCode outta this? I've double- and triple-checked my Base SDK, iOS Deployment Target, Targeted Device Family, in all configurations. I've also tried every option for the compiler version. No dice. I know, XCode, you're running on a Mac, that's great. But I'm coding for an iPhone. Yeesh.
horseshoe7
Member
Mine crashed when trying to add a sprite to two different instances of CCMenuItemSprite.
under 0.99.5b3 it worked fine. The question is, what do I have to do now?
I don't mean to sound like an ass, the term beta means feature complete for that release, all bugs during the alpha phase have been addressed. Introducing API changes and new features when going from a beta to a release candidate is very misleading, and IMHO, not the best way forward.
@horseshoe7: The release notes (which I guess you haven't read) has the changelog. You'll find that 3 bugs were fixed related to menus. In your particular case bugs #458 and #1013 were fixed, and now it is not possible to reuse an item in multiple menus.
See the description of those bugs to understand the reason of it.
As general rule, a child can't have more than 1 parent.
Novaoblivion
Member
Does the attach demo not work for anyone else if using 4.2 (only tested on simulator so far)? All I get is a white screen. Choosing the 4.1 simulator seems to make it work.
I looked through the bugs, and the release notes and didnt see anything but I may have missed it.
@Novaoblivion:
Interesting. I've just tested on the Simulator, and as you said, it doesn't work. But it seems that it works OK on the device. Tested with iPod Touch 4G, iOS 4.2.1
leon34
Member
I'm having the same problem of not being able to link library in simulator mode. I've Xcode 3.2.5 and the base sdk is IOS 4.2 and IOS deployment target is IOS4.2. As soon as I choose the target to be the device all the code lights up in colors but as soon I switch back to simulator mode, XCode seems to forget instantly that there is cocos2d ios linked to this project. I already reinstalled the xcode and also installed the xcode4 preview but both have the same problem as described by rogerimp. Any help would be great.
onegray
Member
@Novaoblivion:
@riq:
I've got the same bug, "Attach Demo" does not work properly in simulator 4.2 (sdk 4.2). Also i noticed, it works fine in case EAGLView frame width is 480 or 320.
You must log in to post.
