Huge problems with SDL 2.0 for x86 Android, and SDL archive

SDL Development
1

Are you running the emulator on Mac or PC?

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: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
Aug 6 12:20:42 Steven-Robichauds-iMac.local emulator-arm[25920] : The function CGSFlushWindow' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use CGSFlushWindowContentRegion’ instead.

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
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

2

So I would just need to download x86 emulator?

And I’m running on mac but I don’t have SDL running yet just the examples the SDK came with would you know the steps to getting SDL off the ground?

What I’ve done so fare is download the Android mac SDK, then Eclipse Mobile and installed the add ons. I comment out the 3 errors from SDL and compiled it with ./configure then make then sudo make install and everything seems to be in the local directory compiled no errors. Then in Eclipse I Create project from existing source and select the android-project folder that was in SDL SDK from mercurial. Not sure if I need more files or I’m not linking SDL? Maybe you would know the steps to settings this environment?

not really in a hurry to get this going but would be nice I’m still working on iOS app but gonna port it to Android as soon as I’m done figured it wouldn’t be a bad idea having a bit of practice

Elmar Krieger wrote:> 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 x86

On 08/06/2012 10:08 PM, Richard Tew wrote:

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)

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! :slight_smile:

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

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

3

Hi Steven,

And I’m running on mac but I don’t have SDL running yet just the
examples the SDK came with would you know the steps to getting SDL off
the ground?

I’m using Linux only, and no Eclipse. I just followed the instructions
in sdl-2.0.0/README.android, and this worked out of the box.

So I would just need to download x86 emulator?

The x86 emulator is only for the new Intel Medfield Atom x86 CPU, which
is sort of a niche in Android:

http://www.anandtech.com/show/5770/lava-xolo-x900-review-the-first-intel-medfield-phone/

If you want to port your app from iOS, then just stay with normal ARM
CPU based Android for the moment.

BTW, in the mean time I could confirm the massive memory corruption on
two computers with nVIDIA and AMD cards, and in both cases it
disappeared when hardware acceleration was disabled. So this is not an
SDL problem, but the Android emulator OpenGL acceleration is broken (at
least in Linux). So while it is tempting to use accelerated OpenGL ES
2.0 in the emulator, it seems like software OpenGL ES 1.0 rendering is
all we get at the moment. I reported the problem to Intel here:

http://software.intel.com/en-us/forums/showthread.php?t=107090

(Maybe Intel one day posts a solution there…)

Best regards,
ElmarOn 08/07/2012 02:03 AM, stevo5800 wrote:

So I would just need to download x86 emulator?

And I’m running on mac but I don’t have SDL running yet just the
examples the SDK came with would you know the steps to getting SDL off
the ground?

What I’ve done so fare is download the Android mac SDK, then Eclipse
Mobile and installed the add ons. I comment out the 3 errors from SDL
and compiled it with ./configure then make then sudo make install and
everything seems to be in the local directory compiled no errors. Then
in Eclipse I Create project from existing source and select the
android-project folder that was in SDL SDK from mercurial. Not sure if I
need more files or I’m not linking SDL? Maybe you would know the steps
to settings this environment?

not really in a hurry to get this going but would be nice I’m still
working on iOS app but gonna port it to Android as soon as I’m done
figured it wouldn’t be a bad idea having a bit of practice

Elmar Krieger wrote:

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:

Quote:

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