Here be dragons. As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible. On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt. Why not use the SDK, out of interest?