What is it?
QConf allows you to have a nice configure script for your qmake-based project. It is intended for developers who don’t need (or want) to use the more complex GNU autotools. With qconf/qmake, it is easy to maintain a cross-platform project that uses a familiar configuration interface on unix.
Part of the rationale for qconf is to piggyback on what Qt already knows. Qt has solved much of the various unix platform differences, in the areas of files, sockets, and even data types. These differences were acknowledged during Qt’s configuration process, and dealt with already, relieving us from this responsibility. For example, no qconf check is needed to determine which data type should be used for an unsigned 32bit integer. Q_UINT32 is your answer. With less checks to perform, qconf is generally faster than the average autoconf script, and has less output.
What do I need to be able to use it?
qconf depends on Qt, obviously.
What features are supported?
- Tested under GNU, BSD, and Solaris environments
- Dependency checking
- Ability to add custom processing
How does it work?
qconf generates a ‘configure’ script that you can copy into your project (it is the only file needed). Running the script will perform some checks, create conf.pri, and run qmake on your .pro file. None of your project files are modified. It is up to you to include conf.pri in your .pro file. See the README for more details.
What is the development plan?
qconf is considered to be complete.
Where can I get it?
Note: QConf may be compiled as a Qt 5 program as of version 2.0. However, it can still generate configure scripts for Qt 4 apps. See the README.md file for information.
The latest source can be found in the ‘qconf’ module of the Psi+ Git.
Last updated December 9th, 2015.
‘wrench’ icon from KDE