summaryrefslogtreecommitdiffstats
path: root/mkspecs/unsupported/android-g++
Commit message (Collapse)AuthorAgeFilesLines
* android: set QMAKE_COMPILERArvid Picciani2012-10-131-1/+2
| | | | | Change-Id: I5b38bf94f0f0d4080b8d355013441c1805524d71 Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
* android-qt: fix build for jellybeanArvid Picciani2012-10-131-1/+5
| | | | | Change-Id: I2a52770502ec6e70ae0e3928d98c6c573f773579 Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
* android-eglfs: open the correct fb device for reading attrsArvid Picciani2012-10-131-1/+68
| | | | | Change-Id: Icedcab50379834fa3456d0e18aaef8a4dd9cf949 Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
* native android support with eglfsArvid Picciani2012-10-043-0/+303
Enable eglfs build against any android > 4 tree, linking to native libs without emulation layers, running on top of surfaceflinger. No GNUs where harmed in the process. Yes, any android. Tested on maguro, tf300, eeepc-x86 x86-64 compiles but broken elsewhere. You don't need an Android.mk, but you must compile from within a shell setup with androids "lunch" or an equivalent that set TOP and OUT. Since we do callbacks to androids build system, the same env restrictions apply (must use gnu bash, and gnumake 3.81) Done-with: Samuel Roedal <samuel.rodal@digia.com> Done-with: Robin Burchell <robin+qt@viroteck.net> Done-with: Brian Avery <brian.avery@nokia.com> Change-Id: Iec0178cdeadbeefc79e4fe6ef449d399ac8ca666 Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>