Doc: Describe creating GUI apps and app bundles using CMake

The default behavior is opposite from when using qmake.

Task-number: QTCREATORBUG-26616
Change-Id: I9ec0f1a961e8d0cb25957dddcceec79cffbf292b
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This commit is contained in:
Leena Miettinen
2021-12-03 17:57:21 +01:00
parent 02f93f68d6
commit 9b4e68dd84

View File

@@ -266,8 +266,16 @@
\b {On Windows:} Output is displayed differently for \e{console \b {On Windows:} Output is displayed differently for \e{console
applications} and \e{GUI applications}. applications} and \e{GUI applications}.
The setting \c {CONFIG += console} in the .pro file specifies that the For qmake projects, the \c {CONFIG += console} setting in the .pro file
application is built as a console application using some other runtime. specifies that the application is built as a console application using
some other runtime.
This is the standard behavior for CMake projects. To create a GUI
application on Windows or an application bundle on \macos, you must
specify the \c WIN32 or \c MACOSX_BUNDLE property for the
\l{https://doc.qt.io/qt-6/qt-add-executable.html}{qt_add_executable}
command in the CMakeLists.txt file.
When you run a console application, you can view the output in the console When you run a console application, you can view the output in the console
window of the calling application. If the window of the calling application. If the
calling application is a GUI application (for example, a release-built calling application is a GUI application (for example, a release-built