Add Qt boostrap to docs

- update the docs to include sections depicting the Qt boostrap.

Author: ShyamQt

doc/source/buildoptions.rst

@@ -64,7 +64,7 @@ options (this list may not be exhaustive):
   for the SDL bootstrap. If multiple orientations are given,
   ``android:screenOrientation`` will be set to ``unspecified``.
 - ``--manifest-orientation``: The orientation that will be set for the ``android:screenOrientation``
-  attribute of the activity in the ``AndroidManifest.xml`` file. If not set, the value 
+  attribute of the activity in the ``AndroidManifest.xml`` file. If not set, the value
   will be synthesized from the ``--orientation`` option.
   The full list of valid options is given under ``android:screenOrientation``
   in the `Android documentation <https://developer.android.com/guide/topics/manifest/activity-element.html>`__.
@@ -74,11 +74,11 @@ options (this list may not be exhaustive):
   ``--home-app`` Gives you the option to set your application as a home app (launcher) on your Android device.
 
   .. Note ::
-    ``--permission`` accepts the following syntaxes: 
+    ``--permission`` accepts the following syntaxes:
     ``--permission (name=android.permission.WRITE_EXTERNAL_STORAGE;maxSdkVersion=18)``
     or ``--permission android.permission.WRITE_EXTERNAL_STORAGE``.
 
-    The first syntax is used to set additional properties to the permission 
+    The first syntax is used to set additional properties to the permission
     (``android:maxSdkVersion`` and ``android:usesPermissionFlags`` are the only ones supported for now).
 
     The second one can be used when there's no need to add any additional properties.
@@ -148,7 +148,7 @@ ready.
   (Which is the default on Android 12+), this setting is not guaranteed to work, and
   you should consider to implement a custom orientation change handler in your app.
 - ``--manifest-orientation``: The orientation that will be set in the ``android:screenOrientation``
-  attribute of the activity in the ``AndroidManifest.xml`` file. If not set, the value 
+  attribute of the activity in the ``AndroidManifest.xml`` file. If not set, the value
   will be synthesized from the ``--orientation`` option.
   The full list of valid options is given under ``android:screenOrientation``
   in the `Android documentation <https://developer.android.com/guide/topics/manifest/activity-element.html>`__.
@@ -187,7 +187,7 @@ You can use this with ``--bootstrap=service_library`` option.
 
 
 This bootstrap can be used together with ``aar`` output target to generate
-a library, containing Python services that can be used with other build 
+a library, containing Python services that can be used with other build
 systems and frameworks.
 
 - ``--private``: The directory containing your project files.
@@ -204,6 +204,49 @@ systems and frameworks.
   include multiple jar files, pass this argument multiple times.
 - ``add-source``: Add a source directory to the app's Java code.
 
+Qt
+~~
+
+This bootstrap can be used with ``--bootstrap=qt`` or by including the ``PySide6`` or
+``shiboken6`` recipe, e.g. ``--requirements=PySide6,shiboken6``. Currently, the only way
+to use this bootstrap is through `pyside6-android-deploy <https://www.qt.io/blog/taking-qt-for-python-to-android>`__
+tool shipped with ``PySide6``, as the recipes for ``PySide6`` and ``shiboken6`` are created
+dynamically. The tool builds ``PySide6`` and ``shiboken6`` wheels for a specific Android platform
+and the recipes simply unpack the built wheels. You can see the recipes `here <https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside-tools/deploy_lib/android/recipes>`__.
+
+.. note::
+  The ``pyside6-android-deploy`` tool and hence the Qt bootstrap does not support multi-architecture
+  builds currently.
+
+What are Qt and PySide?
+%%%%%%%%%%%%%%%%%%%%%%%%
+
+`Qt <https://www.qt.io/>`__ is a popularly used cross-platform C++ framewrok for developing
+GUI applications. `PySide6 <https://doc.qt.io/qtforpython-6/quickstart.html>`__ refers to the
+Python bindings for Qt6, and enables the Python developers access to the Qt6 API.
+`Shiboken6 <https://doc.qt.io/qtforpython-6/shiboken6/index.html>`__ is the binding generator
+tool used for generating the Python bindings from C++ code.
+
+.. note:: The `shiboken6` recipe is for the `Shiboken Python module <https://doc.qt.io/qtforpython-6/shiboken6/shibokenmodule.html>`__
+  which includes a couple of utility functions for inspecting and debugging PySide6 code.
+
+Build Options
+%%%%%%%%%%%%%
+
+``pyside6-android-deploy`` works by generating a ``buildozer.spec`` file and thereby using
+`buildozer <https://buildozer.readthedocs.io/en/latest/>`__ to control the build options used by
+``python-for-android`` with the Qt bootstrap. Apart from the general build options that works
+across all the other bootstraps, the Qt bootstrap introduces the following 3 new build options.
+
+- ``--qt-libs``: list of Qt libraries(modules) to be loaded.
+- ``--load-local-libs``: list of Qt plugin libraries to be loaded.
+- ``--init-classes``: list of Java class names to the loaded from the Qt jar files supplied through
+  the ``--add-jar`` option.
+
+These build options are automatically populated by the ``pyside6-android-deploy`` tool, but can be
+modified by updating the ``buildozer.spec`` file. Apart from the above 3 build options, the tool
+also automatically identifies the values to be fed into the cli options ``--permission``, ``--add-jar``
+depending on the PySide6 modules used by the applicaiton.
 
 Requirements blacklist (APK size optimization)
 ----------------------------------------------

doc/source/commands.rst

@@ -26,15 +26,15 @@ behaviour, though not all commands make use of them.
 
 ``--debug``
   Print extra debug information about the build, including all compilation output.
-  
+
 ``--sdk_dir``
   The filepath where the Android SDK is installed. This can
   alternatively be set in several other ways.
 
 ``--android_api``
   The Android API level to target; python-for-android will check if
   the platform tools for this level are installed.
-  
+
 ``--ndk_dir``
   The filepath where the Android NDK is installed. This can
   alternatively be set in several other ways.
@@ -62,7 +62,7 @@ supply those that you need.
 ``--name NAME``
   The name of the distribution. Only one distribution with a given name can be created.
 
-``--requirements LIST,OF,REQUIREMENTS`` 
+``--requirements LIST,OF,REQUIREMENTS``
   The recipes that your
   distribution must contain, as a comma separated list. These must be
   names of recipes or the pypi names of Python modules.
@@ -74,12 +74,12 @@ supply those that you need.
   The architecture to build for. You can specify multiple architectures to build for
   at the same time. As an example ``p4a ... --arch arm64-v8a --arch armeabi-v7a ...``
   will build a distribution for both ``arm64-v8a`` and ``armeabi-v7a``.
-  
+
 ``--bootstrap BOOTSTRAP``
   The Java bootstrap to use for your application. You mostly don't
   need to worry about this or set it manually, as an appropriate
   bootstrap will be chosen from your ``--requirements``. Current
-  choices are ``sdl2`` (used with Kivy and most other apps) or ``webview``.
+  choices are ``sdl2`` (used with Kivy and most other apps), ``webview`` or ``qt``.
 
 
 .. note:: These options are preliminary. Others will include toggles

doc/source/quickstart.rst

@@ -26,8 +26,8 @@ Concepts
 
 - **bootstrap:** A bootstrap is the app backend that will start your
   application. The default for graphical applications is SDL2.
-  You can also use e.g. the webview for web apps, or service_only/service_library  for
-  background services. Different bootstraps have different additional
+  You can also use e.g. the webview for web apps, or service_only/service_library for
+  background services, or qt for PySide6 apps. Different bootstraps have different additional
   build options.
 
 *Advanced:*
@@ -114,7 +114,7 @@ You need to download and unpack the Android SDK and NDK to a directory (let's sa
 For the Android SDK, you can download 'just the command line
 tools'. When you have extracted these you'll see only a directory
 named ``tools``, and you will need to run extra commands to install
-the SDK packages needed. 
+the SDK packages needed.
 
 For Android NDK, note that modern releases will only work on a 64-bit
 operating system. **The minimal, and recommended, NDK version to use is r25b:**
@@ -214,7 +214,7 @@ website. The default for Flask is 5000.
 Build a Service library archive
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To build an android archive (.aar), containing an android service , you need a name, version, package identifier, explicitly use the 
+To build an android archive (.aar), containing an android service , you need a name, version, package identifier, explicitly use the
 service_library bootstrap, and declare service entry point (See :ref:`services <arbitrary_scripts_services>` for more options), as well as the requirements and arch(s)::
 
     p4a aar --private $HOME/code/myapp --package=org.example.myapp --name "My library" --version 0.1 --bootstrap=service_library --requirements=python3 --release --service=myservice:service.py --arch=arm64-v8a --arch=armeabi-v7a
@@ -281,7 +281,7 @@ Recipe management
 You can see the list of the available recipes with::
 
     p4a recipes
-    
+
 If you are contributing to p4a and want to test a recipes again,
 you need to clean the build and rebuild your distribution::
 
@@ -295,7 +295,7 @@ it (edit the ``__init__.py``)::
 
     mkdir -p p4a-recipes/myrecipe
     touch p4a-recipes/myrecipe/__init__.py
-    
+
 
 Distribution management
 ~~~~~~~~~~~~~~~~~~~~~~~