I'd be willing to take a crack at it. The Android port is built with java and ant, but I could front end it with make. Not sure how I could include the makefile.src/makefile.inc stuff yet, but there's probably a way. The Android native libraries are built a little differently than the standard set of make rules.
Angband on Android
Collapse
X
-
We already have a nightly build set up based on the angband git, details at angdroid.org. Using the Android browser, just tap the link to the nightly apk. When the download is complete, just tap it to pop up the installer.
Not sure what you mean about not wanting an apk? Android only installs apk. Thats like asking for a ride in a car, but not an automobile. Maybe you mean that you want the nightly apk hosted on the Market? Unfortunately I don't know an automated way to make that happen.
Cheers,
GTComment
-
I'd be willing to take a crack at it. The Android port is built with java and ant, but I could front end it with make. Not sure how I could include the makefile.src/makefile.inc stuff yet, but there's probably a way. The Android native libraries are built a little differently than the standard set of make rules.
Do you know anything about building for android on i386 linux? I currently build gcu, x11, gtk, sdl and windows, and would be happy to set up a regular android cross-compile."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
You can totally develop Android apps on Linux. I actually just built a (very) simple one at work. If you google it there are great instructions provided by the Android folks.Comment
-
Sure, but I'm not looking to set up an android dev env from scratch - I'm interested in adding it to my home git environment. For example, to cross-compile for windows I did "sudo apt-get install mingw32" and added a single alias to .bashrc (cd src; make -f Makefile.win -longcrosscompilewibbleoption). I was kinda wondering whether cross-compiling for android can be boiled down to something not much more complex than that ;-)"Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Sure, but I'm not looking to set up an android dev env from scratch - I'm interested in adding it to my home git environment. For example, to cross-compile for windows I did "sudo apt-get install mingw32" and added a single alias to .bashrc (cd src; make -f Makefile.win -longcrosscompilewibbleoption). I was kinda wondering whether cross-compiling for android can be boiled down to something not much more complex than that ;-)
sorry, I see what you are asking now. The short answer is that it really doesn't make sense to cross compile android like that because there's no way to execute the result. To use an emulator or real device you need an apk which can only be produced from a full android dev kit.
Like I mentioned before, I would be willing to invest some time into integrating with the existing angband build system... but the result would still require java and sdk/ndk. At that point the android code could move into git. Probably better for the future to keep all the ports in one place. I'm new to git and reading up on how the merge-into-staging code life cycle works.
Ignore earlier post:
Its not too difficult to set up for android dev either. I use ubuntu to do all android dev. Android apps are java, but call into native code libraries built using the android ndk (native dev kit). These are compiled using ant, and ant in turn executes the appropriate cross compiler bundled in the ndk. At the end everything is bundled into an apk (essentially a java jar file)
here's the steps to set up:
1) install java sdk (I use openjdk-6) and ant
2) download & install latest android sdk and ndk (detailed instructions on developer.android.com)
3) then use ant or eclipse to compile (depends on project -- for angband we just use ant)
4) for angband, get source from http://angdroid.googlecode.com/svn/trunk/, set build.properties, run ant. (details in readme.txt in root dir)Last edited by retrobits; April 15, 2011, 01:46.Comment
-
Playing the Android nightly 3.2.X, (found that version under the Settings/Applications section of the OS) and swapped my known bow for an ego sling and got the following messages:
Illegal object choice (normal)!
You were holding a Long Bow (x3) (+2, +6) (v)
Your bow tingled in your hands
You are shooting with a Sling of Extra Shots (x2) <+1> (splendid) (b)
Would have expected the sling to tingle and not the bow.
Not sure what base nightly the Android version is based on so can't report specifics for it.
Edit. Forgot to add, movement is a pain in the nightly I am playing. Running works but won't allow you to stand on an item to pick it up if in a room, I have to go into preferences and change the move delay setting to 1, then move onto the square to pick up the item. The because I have movement delay setting of 1, every time I want to move a square by tapping the screen the game prompts me for a direction. Means I have to double tap to move one square. Normal Angdroid doesn't have this problem nor does the PC nightly.
Could be I have a setting my preferences that is stuffed, but stuffed if I can work out which one.Last edited by geoff_tewierik; April 18, 2011, 01:39.Comment
-
Edit. Forgot to add, movement is a pain in the nightly I am playing. Running works but won't allow you to stand on an item to pick it up if in a room, I have to go into preferences and change the move delay setting to 1, then move onto the square to pick up the item. The because I have movement delay setting of 1, every time I want to move a square by tapping the screen the game prompts me for a direction. Means I have to double tap to move one square. Normal Angdroid doesn't have this problem nor does the PC nightly.
Could be I have a setting my preferences that is stuffed, but stuffed if I can work out which one.Comment
-
V = April 14th build.
Standard keys.
Also just suffered rapid loss of hit points from "Something makes a strange noise", yet nothing is visible and ?DI shows nothing. Made me dive down a stair rather than harvest Uruks.Comment
-
Comment