fix documentations

.gitignore

@@ -85,6 +85,7 @@ src/CQtDeployer/Deploy/CQtDeployerSingle.json
 src/CQtDeployer/Deploy/QIFWTemplate/config/config.xml
 snap/snapcraft.yaml
 src/LibDeploy/src/deploy_global.h
+doxygen.conf
 
 # binaries 
 testcases/bin/

CMakeLists.txt

@@ -80,6 +80,7 @@ else()
     message("The ${PROJECT_NAME} tests is disabled.")
 endif()
 
+configure_file_in("" "${CMAKE_CURRENT_SOURCE_DIR}/doxygen.conf")
 
 addDoc(${PROJECT_NAME} ${CMAKE_CURRENT_SOURCE_DIR}/doxygen.conf)
 addDeployFromCustomFile("CQtDeployer" "${CMAKE_CURRENT_SOURCE_DIR}/Deploy/CQtDeployer.json")

doxygen.conf.in

@@ -38,20 +38,21 @@ PROJECT_NAME           = CQtDeployer
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         =
+PROJECT_NUMBER         = @CQT_DEPLOYER_VERSION@
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
 # quick idea about the purpose of the project. Keep the description short.
 
-PROJECT_BRIEF          =
+PROJECT_BRIEF          = CQtDeployer helps you to extract all libraries your executable depends on and to create a launch script for your application.
+
 
 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
 # in the documentation. The maximum height of the logo should not exceed 55
 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
 # the logo to the output directory.
 
-PROJECT_LOGO           =
+PROJECT_LOGO           = res/CQtDeployer logo_web.png
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
 # into which the generated documentation will be written. If a relative path is