Application exits immediately if built from source.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Follow the instructions at 
http://code.google.com/p/kwaak3/wiki/BuildInstructions
2. Deploy to the device
3. Observe the application exits immediately

I'm using revision 37 (although I also tried revision 33) built on 32bit Ubuntu 
10.10 with android-ndk-r5b. Running on the Nexus S. Revision 37 required some 
fixes to use the correct path. 

Please provide any additional information below.
I've attached the debug trace. It does not crash but instead exits cleanly. The 
apk's in the Download section work correctly. The source code seems out of date 
compared to these builds, any idea where I can get the latest source?

p.s I'm a software engineer so I'm happy to debug this issue myself, however I 
thought I'd make this ticket to see if anyone else had any similar problems or 
successes. 

Original issue reported on code.google.com by tim...@gmail.com on 11 Apr 2011 at 3:38

Attachments:

• log.txt

[GoogleCodeExporter]

I can confirm this behavior: it shutdown itself cleanly, my log is basically 
the same as your.
I think, however, the downloadable apk version is older than the currently 
available snapshot since one have the option to also enable benchmarking, 
lightmaps and such if building straight from source.

Original comment by manuel....@gmail.com on 16 Apr 2011 at 12:32

[GoogleCodeExporter]

I solved the problem: as i was reading revision comments now i suspect r35 
added support for setMenuState in adroid_input.c and a bunch of other things 
such as setGameDirectory (not used, but i patched jni java bindings to also 
setup it).

Fast-forward to r37, this add the setMenuState method to the native jni module 
but it seems to call a setMenuState method from the KwaakRenderer.java that 
doesn't exists, moreover, the jni-exported method setRenderer is never called 
so the method id also is never initialized.

In order to have it running, please revert r35 changes in the IN_Frame method, 
just comment out the setMenuState call and you should be able to get it running.
Beware! A lot of stuff should be fixed nonetheless!

Attached is a diff with my patches against r37, it's here for completeness, you 
just won't need all my changes to have it running.

Original comment by manuel....@gmail.com on 16 Apr 2011 at 6:43

Attachments:

• r37_running_patch.patch

[GoogleCodeExporter]

I've been having the same issue and I have done as suggested in the comments, 
that is comment out eh line calling setMenuState in the IN_Frame method of 
android_input.c.

However, for me the problem still persists.

Original comment by beniangi...@gmail.com on 26 Jun 2011 at 12:10

[GoogleCodeExporter]

I have been having other issues before this that could be the cause, for more 
information have a look at issue 140.

Original comment by beniangi...@gmail.com on 26 Jun 2011 at 12:17

[GoogleCodeExporter]

I had a look at my logcat and compared it to yours, there is one significant 
difference right before mine dies.

Here is the output before it dies:
Current search path:
//baseq3
0 files in pk3 files
Couldn't load default.cfg
ERROR: couldn't open crashlog.txt

It looks like the path to the baseq3 folder isn't getting set correctly and 
thus it isn't finding the pk3 files, however it checks to make sure they are on 
the sd card and finds them before this point. (if i remove them it complains).

Anyone got any ideas on this issue?

Original comment by beniangi...@gmail.com on 28 Jun 2011 at 1:08

[GoogleCodeExporter]

I have the same problem with it being unable to find the default.cfg and 
exiting.

r34 is the cause of the problem. The author doesn't explain why he removed hard 
coding the path, I can only imagine that he hasn't committed java code changes.

Original comment by leyland....@gmail.com on 28 Aug 2011 at 9:52