---
name: "qmake-module"
section: "5"
platform: "openbsd"
package: "man"
version: "8.0-current-20261101"
release: "OpenBSD 8.0-current (2026-11-01)"
platforms: ["openbsd"]
url: "https://new.carta.tech/qmake-module"
---

# qmake-module(5)

devel/qmake port module

## NAME

**qmake-module** – devel/qmake port module

## DESCRIPTION

This manual page documents the behavior of setting MODULES=devel/qmake in the [ports(7)](/ports/7.md) tree.

This module automates usage of qmake, independently of the actual version of Qt being used. This module requires that one of the *x11/qt\** to be used as well.

If CONFIGURE\_STYLE was not set before, sets its value to ‘qmake’. If CONFIGURE\_STYLE contains ‘qmake’ the module will define each of the *do-build* and *do-install* targets, unless port already defines one; also, SEPARATE\_BUILD will be set to ‘Yes’ unless it's already set to some value. Also, unless NO\_TEST is set, the *do-test* target will be defined.

The following variables could be used in qmake-based ports:

- MODQMAKE\_ARGS

  Additional arguments for qmake invocation. The module already defines some.

- MODQMAKE\_INSTALL\_ROOT

  Root directory for fake install. Normally, it's a WRKINST, but some (broken) ports require another value, like PREFIX.

- MODQMAKE\_PROJECTS

  List of qmake project files to be used, relative to WRKSRC. Directories containing those projects could be used as well, see qmake documentation for details. Defaults to ‘.’, which means the (only) project in WRKSRC directory.

- MODQMAKE\_RECURSIVE

  If ‘Yes’, then qmake will be run recursively during configure stage; otherwise, only projects mentioned in MODQMAKE\_PROJECTS will be processed during configure stage, and their descendants will be visited during main build phase. Sometimes a qmake project processing depends on files generated by other qmake project during build, and recursive builds break this. Defaults to ‘Yes’.

- MODQMAKE\_build

  Actual commands that module will use to build all MODQMAKE\_PROJECTS provided. To be used in complicated cases, when port have to use its own *do-build* target or mix different CONFIGURE\_STYLE values.

- MODQMAKE\_install

  Same as for MODQMAKE\_build, but used in *do-install* stage.

## SEE ALSO

[port-modules(5)](/port-modules/5.md)