Qt4 configuration file

As for the qmake problem, this is fixed by: sudo apt-get install qt5-default. Soma 2 2 gold badges 17 17 silver badges 32 32 bronze badges. JoulC JoulC 31 1 1 bronze badge. On my old RHEL distro, this did it for me: sudo yum install qt-devel.

Michael Fayad Michael Fayad 1, 1 1 gold badge 14 14 silver badges 33 33 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. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 1. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Also, if you want to build with a specific major version, qmake is usually just symlinked to a binary for the default major version.

The real binaries are qmake-qt4 , qmake-qt5 etc. Also see man qtchooser and the qtX-default packages on Debian based systems. There is a bug with qtchooser on Ubuntu This may affect QtCreator also. Here is an example for my system Ubuntu I would suggest to keep both original symlink file and its target in place in case you want to recover the original configuration.

And also create the new files in the default locations for consistency. So here are the steps:. This file must contain two lines: the first line is the path to the Qt binaries including qmake and the second is the path to the Qt libraries including.

In my case it is. Many of the above answers will work. However I have personally found that none of them are persistent.

I can run this command:. But if I open a new terminal and check the Qt version it will revert to the default, and if you have multiple versions of Qt installed the default may not be the one you want. You can tell by running this command:. The only way to make your changes stick is to change the default version. Where you change qt5 to whatever version you want.

You can use the command qtchooser -list-versions to see what versions are installed on your machine. Here are the steps of how to choose the default Qt version for qmake on example of my system Ubuntu As said above. In my case it will be:. In my default setup on Fedora 23 having both qt This was necessary when building the code, not when running the finished QT4 app. For some reason the QT3 path already was installed there permanently and unfortunately at the start of the PATH , which prevented the QT version selector working properly.

I found in Ubuntu Do that by creating the link:. As above, the MyQt. The option may be specified any number of times. All Qt v4 features that have been deprecated in Qt v5 will be disabled. This is useful when porting PyQt4 applications to PyQt5. The PyQt4. The pyuic4 , pyrcc4 and pylupdate4 tools will not be built. This option suppresses the inclusion of the timestamp. The default is platform dependent. Normally qmake is found on your PATH.

This option can be used to specify a particular instance of qmake to use. This option is implied if the --qsci-api-destdir option is specified. Normally sip is found on your PATH. This option can be used to specify a particular instance of sip to use.

The sip. The argument -spec SPEC will be passed to qmake. The default behaviour is platform specific. On Windows configure-ng. On MacOS configure-ng. The PyQt4 modules will be built as static libraries. This is useful when building a custom interpreter with the PyQt4 modules built in to the interpreter.

It is typically used when cross-compiling or when building a static version of PyQt4. By default the version of Python being used to run the configure. It is typically used when cross-compiling. Compiler commands and any output issued during configuration is displayed instead of being suppressed. Use this if configure-ng.

Such arguments are added to any qmake. Normally each PyQt4 module except for the Qt module is linked against the corresponding Qt library. This is useful when linking against static Qt libraries to eliminate the need to distribute the Qt libraries while minimising the memory footprint of the PyQt4 modules.