Hi,
I have upgraded my hybrid project code from 0.12.0 to 0.13.0-beta.
It’s fine on iOS, build ok, run smoothly, everything is perfect.
But when I ran into Android build, it’s fail.
I compared and modified some files including native_build.sh , Android.mk , Application.mk, but they all came to a fail.
Does anybody know how to modify the new hybrid project setting on 0.13.0-beta latest code ?
I am struggle on this for a while.
Thank you in advance.
May be you should paste the error and the Android.mk, Application.mk.
Hi,
Finally, I find the answer. It’s simple, but maybe hard to find it.
The answer is in file “build_native.sh”, there is a path variable named “COCOS2DX_ROOT”.
Actually, it’s not the “COCOS2DX_ROOT” indeed.
If you set this variable like before “…/libs/cocos2dx”, and it will be fail.
You need to set this variable like
COCOS2DX_ROOT=../libs
and do some modifications on Android.mk and Application.mk then your hybrid project is just fine.
I have no time to write the very detail process, but if you have the questions, you may ask here, and I will do my best to answer you.
Thank you.
Dear Minngo：
Now I have my project get compiled on Android, but when I run it, it crash immediately.
I checked the logcat, it shows the error below.
Couldn't load cocosdenshion: findLibrary returned null
I am sure I have added CocosDenshion static library at my Android.mk under jni folder like this :
@
LOCAL_WHOLE_STATIC_LIBRARIES := cocos2dx_static cocosdenshion_static
include $(BUILD_SHARED_LIBRARY)
$(call import-module,CocosDenshion/android) $(call import-module,cocos2dx)
@
What can I do to solve this link or include issue ?
Thank you in advance.
OK…It’s me again…
It’s very strange, every time I ask a question here, sooner or later, I will find the solution by myself. _
The solution is pretty easy, because the CocosDenshion has changed to static library at version 0.13.0-beta.
So you need to mark out the System.loadLibrary("cocosdenshion") at your WhatEverYourGameActivityName.java static {}.
After comment that dynamic library call, I can run my smoothly again.
Finally, I really hope that we can have the update document to save the try and error time.
At least, give us the latest update document, like 0.12.0 to 0.13.0 beta. _
Sorry, we will offer similar document when release next version.
Dear Minggo:
Thank you for your kindness for willing to do this work.
I will have my patience since I know to maintain such a big project isn’t an easy task. _