We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1466 - SDL should optionally(?) not use JNI to improve performance
Summary: SDL should optionally(?) not use JNI to improve performance
Status: RESOLVED DUPLICATE of bug 1383
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: HG 2.0
Hardware: All Android (All)
: P2 enhancement
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-08 15:56 UTC by Ellie
Modified: 2012-05-25 07:36 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2012-04-08 15:56:51 UTC 
As far as I understand it (feel free to close this bug if that is not correct, since it is the only motivation for this request) JNI causes a performance penalty.

Android 4 is here and Android 5 will arrive soon, and Android 2.3 is on the majority of devices. Some developers might want the additional performance SDL as a direct NDK-glued application instead of hassleful JNI-wrapped beast could give them.

Therefore, SDL should optionally not use JNI but operate as pure NDK app as possible since Android 2.3. (Personally, I'd also agree to dropping JNI completely, but I guess others might care more about old devices than me)
Comment 1 Gabriel Jacobo 2012-05-25 07:36:52 UTC 

*** This bug has been marked as a duplicate of bug 1383 ***