[Android-development] Incremental deployment during development with Lollipop
bog_dan_ro at yahoo.com
Tue Jan 13 10:31:33 CET 2015
Sadly run-as doesn't work on most of devices out there and we can't rely on it. My hope is that Google will fix that problem.
From: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt at theqtcompany.com>
To: android-development at qt-project.org
Sent: Tuesday, January 13, 2015 10:59 AM
Subject: Re: [Android-development] Incremental deployment during development with Lollipop
On 01/12/2015 05:23 PM, Harri Pasanen wrote:
> I've been hesitant to update my Nexus 7 to Lollipop as that would kill
> the deploy to tmp folder feature of QC.
> Looking at
> comment #9 would indicate a possible workaround that should be supported
> on Lollipop, and work with Nexus devices at least.
> Has that been tried? If Is there any obvious why it would not work?
> To test it myself, is it enough just to compile my own androiddeployqt,
> or is there code elsewhere as well that needs to be tweaked?
It's a good idea to have this for updated devices that support run-as, I
I think androiddeployqt has to be changed to run the command which
copies the files into the application's sandbox, and then it should
update the android.app.libs_prefix data in the AndroidManifest.xml. For
a proper solution, we should add a placeholder there, like we have with
some of the others. That would mean existing manifests do not get this
feature without being updated, but we can document that in the known
For deploying from the command line, that should be it, I think.
If you want to use Qt Creator for deploying, you also need to change it,
because at the moment it will filter out Lollipop devices if you use
Android-development mailing list
Android-development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Android-development