View Single Post
Posts: 2,076 | Thanked: 3,268 times | Joined on Feb 2011
#260
Originally Posted by w00t View Post
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?
Couple of reasons. First is pleasure to have a fully fledged PC in your pocket (like when flashing one N900 with another, who needs desktop, right?). Second, most of my free-to-tinker time is on bus rides to/from work and similar. If I need a quick fix/modification I can perform it on the go instead of waiting 10h (if I get the idea on the morning ride) to see if it works. Not expecting to have a full build/deploy-to-harbour env on the phone, but for a quick recompile I hope we can make it work (especially now with HWKB OH)


edit: good news, at least tohkbd can be tweaked/tinkered with on the go, qmake generates Makefile correctly, make succeeds, no need for qtcreator

Last edited by szopin; 2014-03-21 at 20:02.
 

The Following 2 Users Say Thank You to szopin For This Useful Post: