If understanding "entry point" of shared library as a function that is invoked when the library is loaded, then on Android it's JNI_OnLoad(). However, I'm not sure what you want to achieve by that. Do you want to hijack the main executable's entry point with your library or something like that :)? If you want to make a user creating single 'main()' function and regardless a platform. Then you're overcomplicating things. You must deliver platform dependent framework that will invoke this function. On Android, you would create simple framework project that loads your library and invokes your "custom" entry point. The REAL entry point on Android starts with JVM, not with the code that runs on it. But as I say, I don't really understand what you want to achieve.

The SDL api uses a #define:

#define main SDL_main

So the user's int main() becomes int SDL_main(), and SDL's library has int WinMain() vs int main(), and etc, based on the OS...

SFML does it without macroes (except on iOS), using this method:

Most of SFML offers the choice of DLLs or static libs, but for one library sfml-main is static linked, and contains the entrypoints and then calls a user-provided standard entrypoint (int main()).

#ifdef SFML_SYSTEM_WINDOWS

#include <windows.h>

extern int main(int argc, char* argv[]);

int WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, INT)
{
    return main(__argc, __argv);
}

#endif // SFML_SYSTEM_WINDOWS

So if one part of your library could be statically linked (or perhaps the whole library, if you don't have any licensing kerfuffles), you could define WinMain() there, and have WinMain call main().

Taking a look into Urho3D they use a macro for the entry point of your program

DEFINE_APPLICATION_MAIN(MyApp)

that is internaly ifdef-ed into the various entry point signatures