Tutorial: cocos2d Xcode Project: Get the latest version of cocos2d-iphone Comments Feed" href="http://www.learn-cocos2d.com/knowledge-base/tutorial-professional-cocos2d-xcode-project-template/feed/"/>

Tutorial: cocos2d Xcode Project: Get the latest version of cocos2d-iphone

Search my cocos2d for iPhone FAQs & Tutorials

Please note that the blog search in the upper right corner doesn’t search my FAQs and Tutorials.
 
  • Note: please do not share direct download links to PDF files, the download links expire after a couple minutes!
< Download cocos2d source code ...
Contributing to cocos2d-iphon... >

As a reminder, here's how to update cocos2d to the latest version.

Download Lesson PDF

Get the latest version of cocos2d-iphone

To update the cocos2d-iphone source code to the latest version, change to the directory where you initially downloaded cocos2d-iphone and enter in Terminal.app:

git pull http://github.com/cocos2d/cocos2d-iphone.git

It's the same command you used to initially download the source code.

Warning: updating cocos2d-iphone may break your code in unexpected ways!

Just a heads up: when you pull a new cocos2d-iphone version from the git repository there's always a chance that changes made to the engine will break your code. Actually, that is very likely to happen. There may be functions removed, parameters added, variables renamed and plenty of other things changed that may cause your code not to compile. Even if your code compiles the changes to the cocos2d engine may introduce strange bugs and weird behavior. First and foremost it is your responsibility to fix these issues, unless of course there's really a bug in the cocos2d engine itself, which can also happen. This extra work is something you have to come to terms with if you want to develop at the bleeding edge of iPhone game development.

The best strategy for you to remain a happy cocos2d-iphone programmer may seem counter-intuitive at first: pull new cocos2d-iphone updates frequently, as often as daily and before you start working on your code. Even if you don't need a specific bugfix or feature. That way, whatever may break it will most likely be very easy to identify and fix. But if you wait weeks or months before doing a cocos2d-iphone engine update, you may actually be better off not doing it at all and instead just use the cocos2d Project Templates and stick to the cocos2d-iphone version you start your project with. Just know that you'll hardly be able to benefit from the latest cocos2d engine bugfixes and features - it's the price you pay for taking the easy route at the start of a project.

There's one exception to the "update cocos2d daily" rule though: if you get close to releasing your game to the App Store, or completing the latest patch for your game, you should not pull the latest cocos2d-iphone version for a while. Especially not at the very last minute. Chances are that something might break that you'll miss but your users will find out about and give you bad reviews because of it. So while you're stabilizing your own build, one of the rules to ensure that your code remains free of bugs and weird side-effects is not to update the underlying game engine, or any code that you haven't written yourself for that matter. Even if the change to the engine may seem trivial - you never know! So wait until after the App or patch is released before you perform another engine update. And by "released" i mean released, not just submitted to Apple for review. You need to be able to quickly submit another build in case of a rejection by Apple.

< Download cocos2d source code ...
Contributing to cocos2d-iphon... >

Comments (1)

  1. hb
    May 14, 2010 21:33

    update cocos2d daily close to release -> its git, just make a branch

Related Questions

Tutorial Poll

What cocos2d or programming How-To/Tutorial would you like me to create? Choose up to three:

View Results

Loading ... Loading ...

148 Responses to “Tutorial: cocos2d Xcode Project: Get the latest version of cocos2d-iphone”

  1. Shamik says:
    July 23, 2010 at 01:41

    Hey,
    is there a guide to integrating the SpaceManager to a normal cocos2d project (one not using your template)? I am trying to do the same and am getting close to 3500 errors. many of them have been listed in the discussions here like ‘stary @ in program’ , but they havent worked for me
    Thanks
    Shamik

    Reply
    • Shamik says:
      July 23, 2010 at 02:02

      when I used SpaceManager0.0.4 it worked just fine, but with 0.0.5 I get those strange and alarmingly large number of errors, what could be the problem?

      Reply
  2. Nmaster64 says:
    September 12, 2010 at 14:28

    What’s the best way to branch a project’s cocos-2d?

    So for example I have my cocos2d folder which I update regularly and which the project is linked to (via method in this tutorial). At some point I decide I no longer want to have the linked version of cocos2d update for this particular project. What’s the best way to go about branching that so the project’s cocos2d no longer update’s when I do that pull.

    If it’s just copy/rename folder and then reconnect, what’s the list of things I have change in the project?

    Thanks for all your help!

    Reply
    • GamingHorror says:
      September 13, 2010 at 12:32

      From the top of my head, I would do:

      - copy and rename the cocos2d folder you want to keep (eg. name it with the version number: “cocos2d-iphone-v0.99.3″)
      - in Xcode, open preferences, go to Source Trees and enter a new setting COCOS2D_SOURCE_0993 and point its path to the cocos2d-iphone-v0.99.3 folder
      - in the project that you wish to keep using 0.99.3, change both (User) Header Search Paths settings to use $(COCOS2D_SOURCE_0993) as their base path instead of $(COCOS2D_SOURCE)

      I think that should be it.

      Reply
  3. Lejon says:
    September 17, 2010 at 16:23

    I have been following this very thorough… but still I am getting build errors.. CClabel not defined…
    What is missing? Which step did I overlook?
    Help would be appreciated!
    Thanks!

    Reply
  4. Lejon says:
    September 17, 2010 at 19:10

    I got it to work, when I added the folder “libs” from the dummy project (temporary cocos2d project described in your tutorial), but this step is not listed, that this folder also needs to be copied… or did I miss something again? :-)

    Reply
  5. Bartek says:
    September 24, 2010 at 15:30

    Really helpful. Especially configuring project for Add-hoc & App Store deployment.

    Reply
  6. Ivor says:
    October 21, 2010 at 21:01

    After completing the “Getting our project to build minimal cocos2d code” I get the following when build and run:

    Undefined symbols:
    “_OBJC_CLASS_$_RootViewController”, referenced from:
    objc-class-ref-to-RootViewController in cocos2dTemplateProjectAppDelegate.o
    ld: symbol(s) not found
    collect2: ld returned 1 exit status

    Reply
  7. Ivor says:
    October 22, 2010 at 16:05

    The latest pulled by git… v0.99.5

    Thanks for the link, I’ll go and try it…

    Reply
  8. A Word About Game Graphics « Just Another iDev says:
    October 31, 2010 at 17:09

    [...] weeks I have been getting approximately 75,000 errors in my project using Cocos2d. I then found this article, and set my project up that way. Works fine [...]

    Reply
  9. Roger says:
    November 2, 2010 at 22:29

    Any recommendations where the ‘cocos2d-iphone folder’ should go..?
    I assume it can go anywhere… but would be interested to hear where people put it.

    Is the Developer folder a sensible place? or should it go in my home folder somewhere?

    Reply
    • Steffen Itterheim says:
      November 2, 2010 at 23:35

      Recently, I’ve changed it so that the reference is to “../cocos2d-iphone” which means cocos2d-iphone and cocos2d-project are both in the same folder. That allows me to copy the project and cocos2d and use seperate cocos2d versions per project. Some older projects for example really don’t need to be updated with the latest cocos2d.

      Reply
      • Roger says:
        November 3, 2010 at 11:30

        err.. I don’t think you understood my question, or maybe I don’t understand how all this stuff works…

        As I see it, somewhere on my hard drive there should be ‘master’ version of cocos2d. This is separate from any projects or templates (I’ve yet to install Cocos2d anywhere on my Mac).

        In your tutorial you say enter the command ‘mkdir cocos2d-iphone’ but where is a good place to create that folder? The Desktop would obviously put a bad place so… where’s a good place?

        Where do people generally keep their frameworks? could I add a ‘Frameworks’ folder to HD/Developer ? will that be effected if/when I update XCode?

        In relation to your reply, I’m guessing this folder could have sub folders holding different versions?

        thanks

        Reply
        • Steffen Itterheim says:
          November 3, 2010 at 12:15

          Ok, I get it. Personally, I have a folder “depot” on HD where all my projects are. But by default I would say that the Documents folder is fine, especially if you add a “Documents/GameProjects/” folder or something similar. Or your user folder ~ so something like ~/GameProjects should be fine too.

          I wouldn’t add it to Developer simply because it’s not supposed to contain user content. And I’ve had one Xcode/iOS SDK bug that forced me to delete Developer and re-install, because a mere re-install didn’t fix the issue.

          But other than that it’s mostly a personal preference where you put your game code.

          Reply
  10. iWalter says:
    November 16, 2010 at 14:33

    Where do you get this file, cocos2d Application.zip ?

    Reply
  11. Peter says:
    November 17, 2010 at 01:43

    Thanks mate, great setup, got it working for the Device.

    With 4.1 there are issues building for the simulator:

    To get it building on the simulator do the following:

    1. Right click on the Targets -> cocos2DXrefTest
    2. Click Get Info from the displayed options.
    3. Click “Base SDK”
    4. Select iOS Simulator 4.0 from the options.
    5. Build and Harry’s your Uncle!

    Regards,
    Peter

    Reply
    • Steffen Itterheim says:
      November 17, 2010 at 11:46

      Actually, you should always set the Base SDK to iOS, never Simulator. Doing so still allows you to deploy to simulator.
      As a matter of fact, iOS SDK 4.2 entirely removed the Simulator SDK from the selection list because it will cause issues when deploying to the device (or may not allow building for the device at all).

      Reply
  12. KaBoom says:
    November 17, 2010 at 15:41

    Hi Steffen.

    After last update of cocos2d my project is not compiled.
    Please take a look on this thread http://www.cocos2d-iphone.org/forum/topic/11150

    Hope you can help me.
    Thanks.

    Reply
    • Steffen Itterheim says:
      November 17, 2010 at 19:53

      I assume you’re referring to my cocos2d-project on github: https://github.com/GamingHorror/cocos2d-project

      I’ve updated it to the latest cocos2d version (0.99.5 RC1) and now it also includes the version of cocos2d that I’ve tested the project with.
      However, I could not reproduce the compiler errors you mentioned but I also can’t exclude that they are in some way or another related to cocos2d-project and upgrading cocos2d-iphone.

      The errors seem odd though. I would try re-installing Xcode respectively the iOS SDK. Ideally, delete or rename the /Developer folder on your hard drive before doing so, to do an absolutely clean install.

      Reply
  13. paris paraskevas says:
    November 21, 2010 at 23:38

    hi Steffen,

    managed to compile and run you template just downloaded from git hub after changing cocos2d-project “base sdk” to “iOS Simulator 4.1″ and “Architectures” set to “optimized” . this is under xcode 4 preview. Oh and compiler set to GCC 4.2 instead of LLVM 2.0

    Although the projects builds and runs with no errors i am getting 2099 issues under box2d. How come? am i doing something wrong or this is normal???

    why xcode 4 and not 3? since i am new to xcode I dont want to learn 3 and by then have to learn ver. 4. i know i cant submit with xcode 4 yet but until my game is done xcode 4 will probably be released!

    Reply
    • Steffen Itterheim says:
      November 22, 2010 at 00:00

      The warnings from Box2D are normal and nothing to worry about.
      Note that you should never set the Base SDK to Simulator, always set it to iOS Device even if you deploy to the Simulator. Apple removed the Simulator SDK option from iOS 4.2.

      Reply
      • Paris says:
        November 22, 2010 at 09:15

        Thanks for your reply Steffen, read that in a post above you said the same thing and changed it to iOS device already

        There are a million settings in Xcode don’t think will ever learn the proper use of each setting, if it compiles and runs at the moment I don’t look further

        Reply
  14. JavaJoe says:
    November 24, 2010 at 21:45

    Thanks for the tutorial Steffen.

    I think a few steps are needed to make this work correctly given the changes you suggest making to the AppDelegate code and differences between class naming of the view controller in OpenGLES projects vs. Cocos2D projects. When you create an OpenGLES project, the ViewController class takes on the name of the project…so, “myproject” would contain myprojectViewController.h/.m, while the cocos2D project creates “RootViewController”

    If you copy the appDelegate code from the cocos2D project and paste over the OpenGLES project’s appDelegate code, the app delegate will now be referencing “RootViewController”. You will need to refactor the appDelegate so that the class is actually RootViewController and will compile successfully.

    Reply
    • Steffen Itterheim says:
      November 24, 2010 at 22:42

      I know, I’ve already done this in the project version I’m currently using. It’s somewhat evolved than the cocos2d-project that’s publicly available. Once I have completed the project I’m working on, I’ll clean up this project and release it (replacing cocos2d-project). This will also add wax (Lua) and ObjectAL support and a few other things.

      Reply
  15. Gabo says:
    November 26, 2010 at 18:28

    Hey, I have a problem with the loading of the cocos2D template. It does not load from the folder where I download it. There is no cocos2D project template when I want to create a new project.

    Can you help me?

    Reply
    • Steffen Itterheim says:
      November 26, 2010 at 20:59

      There’s a little confusion because I used the word “template” without knowing that this is reserved for Xcode templates, in other words the Xcode projects you can create via File -> New. My Xcode template is not that kind of template, it’s a regular Xcode project I use as a template for new project by simply copying the project file and renaming it.

      Reply
« Older Comments

Leave a Reply