Hi,
Am 06.09.2016 um 09:36 schrieb Mitch Curtis:
-----Original Message-----
From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org]
On Behalf Of Wolfgang Baron
Sent: Sunday, 4 September 2016 2:05 PM
To: interest@qt-project.org
Subject: [Interest] Running QtQuick programs in Android virtual device
Hi,
I am trying to run programs containing QtQuick in an Android virtual
device (AVD), so I do not need an army of physical devices for doing
testing. However, running any QtQuick program on any AVD (Windows 10 host,
Qt-5.7, Android x86) I tried gives me a white or a black screen and lots
of error messages about OpenGL.
I have not run all examples from the Qt-5.7 release, but among others, the
gallery applications of QtQuick Controls 1 and 2 fail. Widget programs
like "animatedtiles" work nicely.
Has anone successfully run QtQuick programs on an AVD? Is there a trick to
make AVDs usable for QtQuick development?
Thanks for any hints!
Maybe you're seeing https://bugreports.qt.io/browse/QTBUG-55516?
I don't think so, as the bug talks about a crash in Qt-5.8 due to a
SIGBUS, but I experience a running program using Qt-5.7 with an empty
screen in an Android virtual device (AVD). The program does not react
and I have to explicitly kill the program in the overview view. Warnings
and errors are displayed in the application output window as reported.
Here just a brief example:
W libdrawer_nav_x.so: (null):0 ((null)):
QOpenGLShader::compile(Fragment): Fragment shader failed to compile with
the following errors:
W libdrawer_nav_x.so: ERROR: 0:2: error(#101) Macro redefined: lowp
W libdrawer_nav_x.so: ERROR: 0:3: error(#101) Macro redefined: mediump
W libdrawer_nav_x.so: ERROR: 0:4: error(#101) Macro redefined: highp
W libdrawer_nav_x.so: ERROR: error(#273) 3 compilation errors. No code
generated
I guess developing QtQuick applications is one of the most important
thing to be done on Android, so not being able to test the code on an
AVD before using a physical device is a major complication of the
production process. Most problems can be dealt with using an AVD, so you
could reduce the time having to shuffle around with physical devices.
I think this should be handled like a bug, only I am not quite sure in
which project. Maybe there should even be a fix for the AVDs?
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
