COCOS2DX win732 Environment Construction (Android)

Novice, get a half-day finally set up the environment. Now share the experience of setting up the environment (really novice, maybe some of them are not right, first write down first).

First, the big environment:

1, Windows7 32-bit

2, Cocos2dx V2.3.3 (game engine),

3, Android-ndk-r9d-windows-x86.zip (for compiling C + + in the Eclipse environment),

4, VS2010 (c + + authoring environment, can directly run to see the game writing),

5. Android Developer Tools v22.0.1-685705 (mainly used to release Android, can install Android plugin on eclipse basis), 6, JDK1.6 、

7, Python2.7 (for creating COCOS2DX projects) it seems that much.

Since the original Java project has been written, and occasionally write the C # (. NET) project, Android also occasionally write, more coincidentally, the Python program has also written, so in addition to the above 2nd, 3rd, the others have been installed, So here is the emphasis on COCOS2DX installation of new projects and so on.

First, install the Java environment, all the foundation (Android)

Second, install Python, this is the same as installing the JDK.

Third, COCOS2DX, this is also the SDK, and the above two, this even the environment variables are not written, anyway I did not write, See the tutorial said after the decompression to run the Build-win32.bat file, I do not run here, but the first time to run VS2010 super slow (10 minutes), it is estimated to do the same thing. It is recommended to run first after decompression.

Four,Android-ndk-r9d-windows-x86.zip, this is the same as above three, I did not write environment variables.

Five, tools VS2010, Android development tools, or refer to the online bar, otherwise, not finish.

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

Compared with Unity3d, Cocos2d-x is really just an engine, it does not even develop tools, of course, run, release tools do not, haha (sincerely hope that the great God to make a good thing to do it and u3d A, a whole set of things have).

This is the case after COCOS2DX decompression.

Projects all new projects are placed here, Cocos2d-x-2.2.3\tools\project-creator This directory is used to create the project. This is accompanied by a cow who wrote the tool to create the project (save it as a. bat file and place it in the cocos2d-x-2.2.3\tools\project-creator directory on the line, straight for convenience ):

---------------start (not including this line)------------------------------

@echo off
: Label1
@cls
Echo Welcome to create Cocos2d-x project with Python
set/p project= Please enter the name of the project you want to create:
set/p aid= Please enter the identity name of the Android version package you need to create:
echo the project you entered is named%project%
echo the Android version package you entered is identified with the name%aid%
Does echo confirm the creation of the project?
CHOICE/C 123/m "Confirm please press 1, cancel please press 2, or exit please press 3. "
Echo%errorlevel%
If%errorlevel%==1 Goto Label2
If%errorlevel%==2 Goto Label1
If%errorlevel%==3 Goto LABEL3
: Label2
Echo is creating the project ...
Python create_project.py-project%project%-package%aid%-language CPP
: Label3
Pause

-------------------end (not including this line)-------------------------

here, I have an interesting problem, that is, when the input package name only two paragraphs such as com.test, the creation of the time will be error, the result is that it generated the project is HelloApp. So the recommended package name is above the paragraph. Attach the Create project picture .

At this point, the project has been created, in the Cocos2d-x-2.2.3\projects directory generated the Myngame directory, the structure of the following

Classes is the directory where source files are placed, resources are footage (diagrams, sound files, XML, and so on).

Pro.win32 is available with vs2010 Open, pro.android for Android tools.

Because I only use COCOS2DX to create the Android project, so I will not say the other (in fact, I do not understand *_*).

The following article, detailed in VS2010 development, in ADT Run, released into the APK experience.