mirror of
https://github.com/libsdl-org/SDL.git
synced 2026-05-01 19:44:40 +00:00
Fix SDL_MAIN_USE_CALLBACKS with Android, introduce SDL_MAIN_EXPORTED
My simplification of the conditions for including SDL_main_impl.h had one problem: I forgot that SDL_main_impl.h must be included even on Android when SDL_MAIN_USE_CALLBACKS is used, because then a SDL_main() function that makes sure the callbacks get called is needed, and that function is implemented in SDL_main_impl.h But OTOH, even when SDL_MAIN_USE_CALLBACKS is used, SDL_main_impl.h should not implement a standard `int main(...)` function on Android (because there the SDL-using native code is compiled as a library and the entry point is in SDLActivity.java, which calls SDL_main() in said library). So the check for platforms that don't have *any* native main function but just SDL_main() called from the outside should be handled in SDL_main_impl.h, so both the normal and the callback case can avoid generating a standard main() in the same way. To do this, SDL_MAIN_EXPORTED is defined for platforms like Android, where the real entry point (main() function) is outside of the code that uses SDL, so - SDL_main() must be visibly exported with SDL_DECLSPEC, so the outside code can call it - SDL_main_impl.h must not implement a "real" main() function Another small change based on this is defining SDLMAIN_DECLSPEC at a more general place. If another platform like Android (where the entry point is somewhere else entirely, possibly implemented in a different programming language) turns up, defining SDL_MAIN_NEEDED (so the users main() is renamed to SDL_main()) and SDL_MAIN_EXPORTED should be all that's needed on the SDL_main.h side - and if not then at least the implementation is cleaner and clearer now, IMHO. fixes #11162
This commit is contained in:
committed by
Sam Lantinga
parent
86ef790a23
commit
33366b0a4e
@@ -29,7 +29,7 @@
|
||||
#endif
|
||||
|
||||
/* if someone wants to include SDL_main.h but doesn't want the main handing magic,
|
||||
(maybe to call SDL_RegisterApp()) they can #define SDL_MAIN_HANDLED first
|
||||
(maybe to call SDL_RegisterApp()) they can #define SDL_MAIN_HANDLED first.
|
||||
SDL_MAIN_NOIMPL is for SDL-internal usage (only affects implementation,
|
||||
not definition of SDL_MAIN_AVAILABLE etc in SDL_main.h) and if the user wants
|
||||
to have the SDL_main implementation (from this header) in another source file
|
||||
@@ -64,8 +64,9 @@
|
||||
#endif /* SDL_MAIN_USE_CALLBACKS */
|
||||
|
||||
|
||||
/* set up the usual SDL_main stuff if we're not using callbacks or if we are but need the normal entry point. */
|
||||
#if !defined(SDL_MAIN_USE_CALLBACKS) || defined(SDL_MAIN_CALLBACK_STANDARD)
|
||||
/* set up the usual SDL_main stuff if we're not using callbacks or if we are but need the normal entry point,
|
||||
unless the real entry point needs to be somewhere else entirely, like Android where it's in Java code */
|
||||
#if (!defined(SDL_MAIN_USE_CALLBACKS) || defined(SDL_MAIN_CALLBACK_STANDARD)) && !defined(SDL_MAIN_EXPORTED)
|
||||
|
||||
#if defined(SDL_PLATFORM_WINDOWS)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user