Merge pull request #726 from QuasarApp/task_199

Addee article for building cqtdeployer on arm platforms

doxygen.conf.in

@@ -1215,15 +1215,15 @@ HTML_EXTRA_FILES       =
 # Minimum value: 0, maximum value: 359, default value: 220.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
-HTML_COLORSTYLE_HUE    = 220
+HTML_COLORSTYLE_HUE    = 202
 
 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
 # in the HTML output. For a value of 0 the output will use grayscales only. A
 # value of 255 will produce the most vivid colors.
 # Minimum value: 0, maximum value: 255, default value: 100.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
-HTML_COLORSTYLE_SAT    = 100
+HTML_COLORSTYLE_SAT    = 212
 
 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
 # luminance component of the colors in the HTML output. Values below 100
@@ -1234,7 +1234,7 @@ HTML_COLORSTYLE_SAT    = 100
 # Minimum value: 40, maximum value: 240, default value: 80.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
-HTML_COLORSTYLE_GAMMA  = 80
+HTML_COLORSTYLE_GAMMA  = 59
 
 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
 # page will contain the date and time when the page was generated. Setting this
@@ -1480,7 +1480,7 @@ DISABLE_INDEX          = NO
 # The default value is: NO.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
-GENERATE_TREEVIEW      = YES
+GENERATE_TREEVIEW      = NO
 
 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
 # doxygen will group on one line in the generated HTML documentation.

md/en/Home.md

@@ -20,6 +20,7 @@
 * [Default Environment Variables](EnvironmentVariables.md)
 * [Disable standard shortcuts ](DisableShortcats.md)
 * [Custom scripts](CustomScripts.md)
+* [CQtDeployer for arm](arm.md)
 
 
 ## Support the project

md/en/arm.md

@@ -0,0 +1,63 @@
+# CQtDeployer for arm machines
+
+
+At this time, cqtdeployer does not have precompiled distributions for arm platform. But it supports deploy arm applications, so the best solution for install cqtdeployer tool to arm host is building from source.
+
+## Build
+
+You can read a main article of building cqtdeployer from source [here](Build-and-Install.md).
+
+## Qt installer framework.
+
+The QIFW not available for arm platforms. So if you want to create classic installers you need to build Qt installer framework from [source](https://github.com/qtproject/installer-framework).
+
+## Build from source
+
+- clone project 
+
+    ``` bash
+    git clone https://github.com/QuasarApp/CQtDeployer.git
+    git submodule update --init --recursive
+    cd CQtDeployer
+    ```
+
+- create temp build directory
+
+    ``` bash
+    mkdir build 
+    cd build
+    ```
+
+- Install qt from package manager (for example apt on ubuntu)
+
+    ``` bash
+    sudo apt install qt6-base-dev
+    ```
+
+- run cmake 
+
+    ``` bash
+    cmake .. -DBUILD_SHARED_LIBS=0 -DCQT_DEPLOYER_TESTS=0
+    ```
+
+- build cqtdeployer 
+
+    ``` bash
+    make -j8
+    ```
+
+- create cqtdeployer executable.
+
+    ``` bash
+    make install 
+    ```
+
+
+Done. Now you can add cqtdeployer into your PATH variable and use it or create symbol link to cqtdeployer executable in /bin folder.
+
+
+``` bash
+ln -s ./bin/CQtDeployer /bin/cqtdeployer
+```
+
+

md/ru/Home.md

@@ -9,7 +9,6 @@
 * [Параметры](Options.md)
 * [Руководство](Guide.md)
 * [Краткое Руководство](QuickGuide.md)
-* [Сборка и установка](Build-and-Install.md)
 * [Файл развертывания](DeployConfigFile.md)
 * [Упаковка](Packing.md)
 * [Список изменений](Changelog.md)