Dear SDLers,
I’ve 10 years of extensive SDL experience, but my attempt to port my
application to x86 Android (i.e. Android running on Intel’s Medfield
Atom CPU) is currently hitting a wall of memory corruption and other
problems already at the very basic level, so that I can’t even get a
"Hello World" running.
Before I go into details: Has anyone of you ever successfully built and
run an SDL 2.0 application in one of Intel’s two currently available
Android Virtual Devices
“Intel Atom x86 System Image (Intel Corporation) - API Level 10”
(Android 2.3)
or
“Android 4.0.3 API Level 15” (Intel Atom x86)
If yes, which application, and where can it be downloaded?
If I have at least one working example, things will get easier to trace
down.
BTW, searching the mailing list archive at
http://lists.libsdl.org/pipermail/sdl-libsdl.org/
does currently not work, I always get 0 hits (e.g. for keyword android)
Many thanks for your help,
Elmar
Just to confirm about the search mechanism. I tried that too, and it seems totally broken, atm.-------------------------------------------------------
Currently working on M.U.L.E. Returns (http://mulereturns.com/)
On Monday, August 6, 2012 at 4:10 PM, Elmar Krieger wrote:
Dear SDLers,
I’ve 10 years of extensive SDL experience, but my attempt to port my
application to x86 Android (i.e. Android running on Intel’s Medfield
Atom CPU) is currently hitting a wall of memory corruption and other
problems already at the very basic level, so that I can’t even get a
"Hello World" running.
Before I go into details: Has anyone of you ever successfully built and
run an SDL 2.0 application in one of Intel’s two currently available
Android Virtual Devices
“Intel Atom x86 System Image (Intel Corporation) - API Level 10”
(Android 2.3)
or
“Android 4.0.3 API Level 15” (Intel Atom x86)
If yes, which application, and where can it be downloaded?
If I have at least one working example, things will get easier to trace
down.
BTW, searching the mailing list archive at
http://lists.libsdl.org/pipermail/sdl-libsdl.org/
does currently not work, I always get 0 hits (e.g. for keyword android)
Many thanks for your help,
Elmar
SDL mailing list
SDL at lists.libsdl.org (mailto:SDL at lists.libsdl.org)
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
I am currently running my SDL 2.0 application in the emulator named
above this paragraph. I am also selling it with x86 binaries on the
Android store:
https://play.google.com/store/apps/details?id=org.disinterest.broguex
The sale statistics do not give a breakdown of what architecture is
being used by which installee. The source code to a stripped down
version is here:
https://bitbucket.org/jice/libtcod
If you compile the modified version of the SDL2 Android starter
project which comes with that, then it should work for you. I don’t
believe it is set up to compile x86 by default, but you know how to do
that. If it doesn’t work… then I imagine that something is wrong
with your environment. Note that I am using revision efd48af40ec3,
just because I am too lazy to merge. My only modifications are the
currently outstanding Android keyboard patch in bugzilla, as the
existing keyboard mapping is very limited and insufficient for normal
keyboard use.
Hope this helps! 
Cheers,
Richard.On Tue, Aug 7, 2012 at 3:10 AM, Elmar Krieger wrote:
I’ve 10 years of extensive SDL experience, but my attempt to port my
application to x86 Android (i.e. Android running on Intel’s Medfield Atom
CPU) is currently hitting a wall of memory corruption and other problems
already at the very basic level, so that I can’t even get a "Hello World"
running.
Before I go into details: Has anyone of you ever successfully built and run
an SDL 2.0 application in one of Intel’s two currently available Android
Virtual Devices
“Intel Atom x86 System Image (Intel Corporation) - API Level 10” (Android
2.3)
Hi Richard,
many thanks for your reply. I now got one step further and caught the
emulator reproducibly overwriting parts of my application’s memory as
soon as the emulation uses OpenGL hardware acceleration, instead of
software rendering.
Since this is such a severe problem, my guess is that this affects my OS
(Linux) only, but not Windows/MacOSX. Am I right that you are using
Windows or MacOSX to develop your application?
Best regards,
Elmar
P.S.: To stevo5800:
I just downloaded it on Mac and the emulator it self is slow and it
seems that it uses Quartz now also I get these error message on launch
Starting emulator for AVD 'Android4.1’
2012-08-06 12:20:42.500 emulator-arm[25920:f07] Warning once:
‘emulator-arm’ looks like the normal ARM emulator, not the Intel x86On 08/06/2012 10:08 PM, Richard Tew wrote:
On Tue, Aug 7, 2012 at 3:10 AM, Elmar Krieger<@Elmar_Krieger> wrote:
I’ve 10 years of extensive SDL experience, but my attempt to port my
application to x86 Android (i.e. Android running on Intel’s Medfield Atom
CPU) is currently hitting a wall of memory corruption and other problems
already at the very basic level, so that I can’t even get a "Hello World"
running.
Before I go into details: Has anyone of you ever successfully built and run
an SDL 2.0 application in one of Intel’s two currently available Android
Virtual Devices
“Intel Atom x86 System Image (Intel Corporation) - API Level 10” (Android
2.3)
I am currently running my SDL 2.0 application in the emulator named
above this paragraph. I am also selling it with x86 binaries on the
Android store:
https://play.google.com/store/apps/details?id=org.disinterest.broguex
The sale statistics do not give a breakdown of what architecture is
being used by which installee. The source code to a stripped down
version is here:
https://bitbucket.org/jice/libtcod
If you compile the modified version of the SDL2 Android starter
project which comes with that, then it should work for you. I don’t
believe it is set up to compile x86 by default, but you know how to do
that. If it doesn’t work… then I imagine that something is wrong
with your environment. Note that I am using revision efd48af40ec3,
just because I am too lazy to merge. My only modifications are the
currently outstanding Android keyboard patch in bugzilla, as the
existing keyboard mapping is very limited and insufficient for normal
keyboard use.
Hope this helps!
Cheers,
Richard.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
–
Elmar Krieger, PhD
YASARA Biosciences GmbH & CMBI Outstation Austria
Wagramer Strasse 25/3/45
1220 Vienna
Austria/Europe
www.YASARA.org
Hi Richard,
many thanks for your reply. I now got one step further and caught the
emulator reproducibly overwriting parts of my application’s memory as soon
as the emulation uses OpenGL hardware acceleration, instead of software
rendering.
Since this is such a severe problem, my guess is that this affects my OS
(Linux) only, but not Windows/MacOSX. Am I right that you are using Windows
or MacOSX to develop your application?
Yes, I am using Windows to develop, and for that matter software rendering.
I have never been able to get hardware accel. To work.
Cheers,
Richard.On Tuesday, August 7, 2012, Elmar Krieger wrote: