[Android-development] On False Promises ...

[Rubi Mazaki]

Yepp, sorry - I meant *ANDROID_PACKAGE_SOURCE_DIR*=AndroidManifest.xml
which allows to override the AndroidManifest.xml

AND !


Deploy configurations - this is minimized by default!! ... wow - this one
is BAD (in my humble opinion ...) why put it minimized if anyone deploying
to android will have to use it.

Do you understand that using Qt until now, there was simply no reason to
unfold this panel? I totally missed it!

And no. I don't ever read documentations :) lest other do that :) :)





With Regards,

Rubi Mazaki
Email: rubimazaki at gmail.com


On Wed, Jan 8, 2014 at 5:07 PM, Eskil Abrahamsen Blomfeldt <
eskil.abrahamsen-blomfeldt at digia.com> wrote:

>  On 01/07/2014 05:25 PM, Rubi Mazaki wrote:
>
>   AFAIK https://bugreports.qt-project.org/browse/QTBUG-35529 regards to
> the way the examples are shipped, which is less critical in my opinion. The
> problem with the Android installation is that it provides examples that
> don't work 90% of the time. And that's really bad. As to the android tag, I
> must say that the existence of the tags was not something I was much aware
> of until now, so I guess that is the experience of a new/desktop Qt user,
> trying to start mobile dev.
>
>  Regarding the AndroidManifest.xml - I guess it would be great if qt
> builder would handle the permission management automatically, but as it
> seems, after running a number of samples, non of them installed with any
> permissions. So, it seems that Qt just don't handle this, which is
> critical. WORSE, to override the AndroidManifest one must go and find the
> right line to write in the .pro file, a line that is not documented:
>
>
> No, the default manifest contains the following permissions:
>
> <uses-permission android:name="android.permission.INTERNET"/>
> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
>
> If you depend on something that requires special permissions, such as
> multimedia or positioning, then the permissions for these will also be
> added automatically to your manifest.
>
>
> *in QMAKE:*
> *ANDROID_DEPLOYMENT_DEPENDENCIES*=<dir_conaining_AndroidManifest.xml_path>
>
>
> No, this is a huge misunderstanding. That line has nothing to do with the
> manifest file whatsoever. Please read the documentation here:
>
>     http://qt-project.org/doc/qt-5/deployment-android.html#qmake-variables
>
> If you are using Qt Creator, you can add a manifest by pushing the "Add
> Manifest" button instead of editing the .pro file. There's a limit to how
> intuitive this can be done and still be a useful UI for expert users, so I
> would recommend reading the documentation for Creator as well when problems
> arise.
>
>
>
>  *in QBS (available?)*
>  MANIFEST command line variable
>
>
> QBS does not properly support Android at the moment. That's a work in
> progress.
>
> -- Eskil
>
> _______________________________________________
> Android-development mailing list
> Android-development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/android-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/android-development/attachments/20140108/839c3902/attachment.html>