25b36d900a
Previously, we included the stubs in our driver binaries, so they didn't call the actual system libraries for these functions. This was enough to build-test the Android code in CI without even the NDK. To make NDK-built Mesa drivers useful, we need to link against these system libraries that aren't present in the NDK. Split the symbols to separate non-installed shared libraries and link against those, so that when you drop the resulting .so in your /vendor/lib64/hw/, it just works out. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6805> |
||
|---|---|---|
| .. | ||
| README.md | ||
| backtrace_stub.cpp | ||
| cutils_stub.cpp | ||
| hardware_stub.cpp | ||
| log_stub.cpp | ||
| meson.build | ||
| sync_stub.cpp | ||
README.md
The Android NDK doesn't come with enough of the platform libraries we need to build Mesa drivers out of tree, so android_stub has stub versions of those library that aren't installed which we link against, relying on the real libraries to be present when the Mesa driver is deployed.