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 3314

Summary: Add a way to query if SDL was compiled with SDL_ANDROID_BLOCK_ON_PAUSE
Product: SDL Reporter: prismatic.project
Component: buildAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: philipp.wiesemann
Version: 2.0.4   
Hardware: All   
OS: Android (All)   

Description prismatic.project 2016-05-01 17:09:21 UTC 
As far as I can tell there's no way to check whether or not SDL is compiled with the SDL_ANDROID_BLOCK_ON_PAUSE option. Since an application may have to be structured differently based on this option it would help to have an easy way to check.

Also a related thought: Is there any reason that SDL_ANDROID_BLOCK_ON_PAUSE is a compile-time option? It'd be more flexible if the option could be set as a hint or something with SDL's API.
Comment 1 Ryan C. Gordon 2018-08-06 21:20:23 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.