Product version. Comma delimit 4 numbers eg. Display the SVN version number in the build log. All rights reserved. Replies: 5 Last Post: 6th May , How to define "Post-Build Event" for vcproj using qmake?
By mgrusz in forum Qt Tools. Replies: 2 Last Post: 17th October , Replies: 2 Last Post: 7th October , Replies: 1 Last Post: 4th December , Define compiler in qmake By philski in forum Newbie. Specifies the version number of the application if the app template is specified or the version number of the library if the lib template is specified.
On Windows, triggers auto-generation of an. The generated. Each number must be in the range from 0 to Specifies the version number, that the Windows linker puts into the header of the. Only a major and minor version may be specified. Specifies the major version number of the library if the lib template is specified. Specifies the minor version number of the library if the lib template is specified.
Specifies the patch version number of the library if the lib template is specified. Tells qmake where to search for files it cannot open. Specifies the targeted Windows version; this corresponds to the tag WindowsTargetPlatformVersion in vcxproj files.
Specifies the minimum version of the Windows target platform; this corresponds to the tag WindowsTargetPlatformMinVersion in vcxproj files. Specifies parameters to be passed to the application manifest on UWP.
The allowed values are:. In case the input manifest file should not be processed and only copied to the target directory, the verbatim configuration needs to be set. Specifies a list of Yacc source files to be included in the project. All dependencies, headers and source files will automatically be included in the project. For example, the following line causes the location of the project file to be written to the console:. For example, the following line causes the location of the directory containing the project file to be written to the console:.
Documentation contributions included herein are the copyrights of their respective owners. Qt and respective logos are trademarks of The Qt Company Ltd. All other trademarks are property of their respective owners. Variables The fundamental behavior of qmake is influenced by variable declarations that define the build process of each project.
Option Description release The project is to be built in release mode. If debug is also specified, the last one takes effect. Note: The details are slightly different when producing Visual Studio and Xcode projects. When this option is enabled, qmake will create a file with the extension. Option Description qt The target is a Qt application or library and requires the Qt library and header files.
The proper include and library paths for the Qt library will automatically be added to the project. The proper include paths and libraries will automatically be added to the project. A check target will be added to the generated Makefile to run the test. Only relevant when generating Makefiles. Only relevant if testcase is also set. The proper include paths, compiler flags and libraries will automatically be added to the project.
Consider using the option cmdline for cross-platform applications. Note that dll can also be used on all platforms; a shared library file with the appropriate suffix for the target platform. The proper compiler flags will automatically be added to the project.
This enables dll as well. Option Description flat When using the vcapp template this will put all the source files into the source group and the header files into the header group regardless of what directory they reside in. This is turned on by default. This value is not supported by the Xcode project generator. Option Description largefile Includes support for large files. Note: This variable is used only on Windows when using the app template. Use this config value if you need to install files that are generated as part of your build process, like HTML files created by qdoc.
If you don't want this behavior, set this config value to ensure that the build target is not added as a dependency to the install target. But, if you have an install target with this config value set, it's not installed by default. Note: Do not attempt to overwrite the value of this variable. Keys Values. Note: Most of the time, the default Info. Note: This variable is used for Visual Studio project files only. Note: Specifying the provisioning profile disables the automatically managed signing.
Note: This variable is used on the watchOS platform only. Modifier Effect. Cannot be used in conjunction with. Available only on platforms that use makefiles. Option Description app Creates a Makefile for building applications the default. See Building an Application for more information. See Building a Library for more information. Use this if no compiler needs to be invoked to create the target; for instance, because your project is written in an interpreted language.
Member Description architecture The target architecture. Defaults to green. Currently, verbatim is the only available option. Defaults to "en". Defaults to Default package description. Defaults to light. Default provided by the mkspec. This parameter is obsolete. This is supported on all Windows Store App platforms.
This has to be x pixels. Supported on all Windows Store App platforms. The image must have a pixel size of 70x The image must have a pixel size of 30x The image must have a pixel size of x Defaults to Default publisher display name. Defaults to 1. The project is to be built in release mode. This option is set by default. Automatically generates a. When using the subdirs template, this option specifies that the directories listed should be processed in the order in which they are given.
Enables support for the use of precompiled headers in projects. Enables support for the use of precompiled headers for C files. The compiler should output as many warnings as possible. Thread support is enabled. Specifies that the project's source files use the UTF-8 encoding. By default, the compiler default is used.
Set the default visibility of symbols in the binary to hidden. C99 support is enabled. This option has no effect if the compiler does not support C99, or can't select the C standard. C11 support is enabled. This option has no effect if the compiler does not support C11, or can't select the C standard. C17, also known as C18, support is enabled. This option has no effect if the compiler does not support C17, or can't select the C standard. By default, support is enabled. By default, support is disabled.
By default, this option is disabled. Not set by default. Requires lrelease to be set, too. By default, qmake does not compile source files that are included in other source files. This option disables this behavior. This option enables qmake to track these dependencies. When this option is enabled, qmake will process all libraries linked to by the application and find their meta-information see Library Dependencies for more info.
The target is a Qt application or library and requires the Qt library and header files. The target is an X11 application or library. The target is an automated test. The exit code of the automated test will be ignored. The target is a Win32 window application app only. The target is a Win32 console application app only. The target is a cross-platform command line application. The target is a static library lib only. Ensures that the list of libraries stored in the LIBS variable is not reduced to a list of unique values before it is used.
When using the vcapp template this will put all the source files into the source group and the header files into the header group regardless of what directory they reside in. Puts the plugin into a plugin bundle. If not set, qmake looks to see if the files to install actually exist. If set, the typical Unix strip functionality is turned off and the debug information will remain in the binary.
When you do a make install , and you don't have a build of the project yet, the project is first built, and then installed. A project has a top-level project target where, when you do a make install , everything is installed. Expands to the target bundle's bundle identifier string, for example: com. Specify the subproject pro file explicitly. Base string used for makefile targets related to this subproject. Creates a Makefile for building applications the default.
Creates a Makefile for building libraries. Creates a Makefile for building targets in subdirectories. Creates a Makefile for not building anything. Once you have the. If you are still using qmake to generate your makefiles, you need to add a single line to your. Finally, regenerate your makefile and your application. However, if you already have an. First, put a single line of text to the myapp. If you do not use qmake , the necessary steps are: first, create an.
The application icon, typically displayed in the application dock area, is set by calling QWindow::setWindowIcon on a window. It is possible that the program could appear in the application dock area before the function call, in which case a default icon will appear during the bouncing animation. To ensure that the correct icon appears, both when the application is being launched, and in the Finder, it is necessary to employ a platform-dependent technique.
Although many programs can create icon files. Using this tool also compresses the resulting icns file, so there is no need for you to perform additional compression.
To configure the application's icon, the Info. This can be achieved by setting the. If you are still using qmake to generate your makefiles, you only need to add a single line to your. For example, if the name of your icon file is myapp. This will ensure that qmake puts your icons in the proper place and creates an Info.
0コメント