Android Misery just one typo away
All of us open source hacks have at least some duty to report landmines to
the rest.
2 years?
Burned as well.
More prominent in the docs?
The docs could serve a wider audience by adding in landmines
notes in each section where there is a reported
It's certainly one of the uglier gotchas people run into. Here is my humble
attempt to document it more prominently:
https://codereview.qt-project.org/#/c/114517/
Anyhow, adding stuff to the documentation only helps so much, since people
also have to read it :)
In general, I consider
On 2015-06-15 19:10, Thiago Macieira wrote:
On Monday 15 June 2015 10:17:48 mark diener wrote:
It WILL compile on all the platforms, runs fine on OSX/IOS Simulator,
but
on Android it will surely DIE.
In addition to what the others said, run fine is missing a
characterisation.
Your
On Monday 15 June 2015 10:17:48 mark diener wrote:
It WILL compile on all the platforms, runs fine on OSX/IOS Simulator, but
on Android it will surely DIE.
In addition to what the others said, run fine is missing a characterisation.
Your program is running under undefined behaviour because the
Hello list folk:
Under OSX/IOS, no problem.
Under Android, nasty and obscure segment fault
Qt 5.4.2, NDK 10e
Do NOT under any circumstance forget the before the argc parameter on
the constructor
if you override QGuiApplication (QApplication too)
Good:
Trpzapp::Trpzapp(int argc, char** argv)
function overload.
Scott
From: interest-bounces+scott.bloom=onshorecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf Of
mark diener
Sent: Monday, June 15, 2015 10:18 AM
To: interest@qt-project.org
Subject: [Interest] 5.4.2 Android Misery just one
On 15 Jun 2015, at 19:17, mark diener rpzrpz...@gmail.com wrote:
Hello list folk:
Under OSX/IOS, no problem.
Under Android, nasty and obscure segment fault
Qt 5.4.2, NDK 10e
Do NOT under any circumstance forget the before the argc parameter on the
constructor
if you override
