Where is qtdir set

Collectives on Stack Overflow. Learn more. Asked 4 years, 1 month ago. Active 4 years, 1 month ago. Viewed 6k times. Improve this question.

Add a comment. Active Oldest Votes. Solution 1. Solution 2. Enjoy building the project. Restart MS VS could be required. Improve this answer. Community Bot 1 1 1 silver badge. Suresh Namala Suresh Namala 3 3 silver badges 11 11 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Learn More. Ask a question. Quick access. Search related threads. It was removed in kdesrc-build 1.

Online API documentation is available from kde. This option enables the asynchronous mode of operation, where the source code update and the build process will be performed in parallel, instead of waiting for all of the source code updates before starting the build process. This option defaults to enabling asynchronous mode. To disable, set this option to false.

Set this option to set the environment variable PATH while building. You cannot override this setting in a module option. This environment variable should include the colon-separated paths of your development toolchain. Set this option to checkout from a branch of KDE instead of the default of master for Git modules or trunk for Subversion , where KDE development occurs. For instance, to checkout KDE 4. If kdesrc-build fails to properly download a branch with this option, you may have to manually specify the URL to download from using the module-base-path or override-url options.

For most KDE modules you probably wish to use the branch-group option instead and use this option for case-by-case exceptions. For supported Git module types, kdesrc-build will determine the actual branch to use automatically based on rules encoded by the KDE developers these rules may be viewed in the kde-build-metadata source repository in your source directory. After a branch is determined that branch is used as if you had specified it yourself using the branch option.

This is useful if you're just trying to maintain up-to-date on some normal development track without having to pay attention to all the branch name changes. Note that if you do choose a branch yourself, that it will override this setting. The same is true of other specific branch selection options such as tag. This option only applies to kde-projects Git modules the common case. Relative to the KDE Subversion source directory see the source-dir option.

Absolute path. Relative to your home directory. Use this option in order to control whether kdesrc-build always tries to build a module that has not had any source code updates. By setting build-when-unchanged to true , kdesrc-build always attempts the build phase for a module, even if the module did not have any source code updates. This is the default setting since it is more likely to lead to a correct build. By setting build-when-unchanged to false , kdesrc-build will only attempt to run the build phase for a module if the module has a source code update, or in other situations where it is likely that a rebuild is actually required.

This can save time, especially if you run kdesrc-build daily, or more frequently. This feature is provided as an optimization only. Like many other optimizations, there are trade-offs for the correctness of your installation.

For instance, changes to the qt or kdelibs modules may cause a rebuild of other modules to be necessary, even if the source code doesn't change at all. Set this option to checkout Subversion sources piece by piece.

The value for this option should be a space-separated list of directories to checkout. Although this option overrides the global option, be aware that setting this as a global option makes no sense.

Note that this setting has no effect on Git modules due to the operation of the Git source control system. Use this option to specify which generator to use with CMake. Invalid unsupported values are ignored and treated as if unset.

If not set Unix Makefiles will be used by default. Note that if a valid generator is also specified through cmake-options it will override the value for cmake-generator. When a valid toolchain file is configured, kdesrc-build will no longer set environment variables automatically.

You can use set-env , binpath and libpath to fix up the environment manually if your toolchain file does not work out of the box with kdesrc-build. Refer to the overview of standard flags added by kdesrc-build for more information.

Note that if a valid toolchain is also specified through cmake-options it will override the value for cmake-toolchain. Use this option to specify what flags to pass to CMake when creating the build system for the module. When this is used as a global option, it is applied to all modules that this script builds.

When used as a module option, it is added to the end of the global options. This allows you to specify common CMake options in the global section. This option does not apply to qt which does not use CMake. Use configure-flags instead. If a valid generator is specified among the listed options it will override the value of cmake-generator. Invalid unsupported generators are ignored and will not be passed to CMake. If a valid toolchain file is specified among the listed options it will override the value of cmake-toolchain.

Invalid toolchains are ignored and will not be passed to CMake. Since these options are passed directly to the CMake command line, they should be given as they would be typed into CMake. For example:. Since this is a hassle, kdesrc-build takes pains to ensure that as long as the rest of the options are set correctly, you should be able to leave this option blank.

In other words, required CMake parameters are set for you automatically. This option defaults to true , set it to false to disable this behavior. This option defaults to false , set it to true to enable the automatic symbolic link creation. Use this option to specify what flags to pass to. When this is used as a global-option, it is applied to all modules that this script builds. This option only works for qt. To change configuration settings for KDE modules, see cmake-options.

This option can be set to run a different command other than make , for example in order to perform the build process.

However it can be useful to use alternate build systems. The value of this option is used as the command line to run, modified by the make-options option as normal.