The SDL forums have moved to discourse.libsdl.org.
This is just a read-only archive of the previous forums, to keep old links working.

NVidia has released some pretty nice Tegra profiling tools for their Android devices. The NVidia Tegra Graphics Debugger works by providing an interposer library that intercepts ES2 and EGL calls. You must link against these libraries.
Unfortunately, this quietly fails with SDL2 because libEGL and libGLES2 are dynamically loaded with dlopen().

NVidia offers a secondary approach to using the Tegra Graphics Debugger: root your device and install a global interposer library. Almost no devs will try this first if they don’t have a rooted device, leading to heaps of wasted time failing to attach the profiler.

I propose an update to the Android readme that explains why the static linking approach recommended by NVidia doesn’t work.

I have filed a bug, with proposed wording for the readme in the description, here:
https://bugzilla.libsdl.org/show_bug.cgi?id=2983

Michael Labbé

NVidia has released some pretty nice Tegra profiling tools for their Android devices. The NVidia Tegra Graphics Debugger works by providing an interposer library that intercepts ES2 and EGL calls. You must link against these libraries.
Unfortunately, this quietly fails with SDL2 because libEGL and libGLES2 are dynamically loaded with dlopen().

NVidia offers a secondary approach to using the Tegra Graphics Debugger: root your device and install a global interposer library. Almost no devs will try this first if they don’t have a rooted device, leading to heaps of wasted time failing to attach the profiler.

I propose an update to the Android readme that explains why the static linking approach recommended by NVidia doesn’t work.

I have filed a bug, with proposed wording for the readme in the description, here:
https://bugzilla.libsdl.org/show_bug.cgi?id=2983

Michael Labbé