QMAKE-MODULE(5)

📦 in nixpkgs unstable

🎀 NAME 🎀

qmake-module — the devel/qmake port module. Bestie, this is qmake-module(5) from the File Formats Manual, and we're about to make it make sense. ✨

💖 DESCRIPTION 💖

Okay so this manual page documents the behavior of setting MODULES=devel/qmake in the ports(7) 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* is used as well. 💅

If CONFIGURE_STYLE was not set before, the module sets its value to qmake. If CONFIGURE_STYLE contains qmake, the module will define each of the do-build and do-install targets, unless the 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 the qmake invocation. The module already defines some, so this is your extra-little-something slot. 🌸
  • MODQMAKE_INSTALL_ROOT — root directory for fake install. Normally, it's a WRKINST, but some (broken) ports require another value, like PREFIX. Yeah, broken ports stay doing broken-port things. 😭
  • 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 the WRKSRC directory. 🦋
  • MODQMAKE_RECURSIVE — if Yes, then qmake will be run recursively during the configure stage; otherwise, only projects mentioned in MODQMAKE_PROJECTS will be processed during the configure stage, and their descendants will be visited during the main build phase. Sometimes a qmake project processing depends on files generated by another qmake project during build, and recursive builds break this. Defaults to Yes. 💀
  • MODQMAKE_build — actual commands that the module will use to build all MODQMAKE_PROJECTS provided. To be used in complicated cases, when a port has to use its own do-build target or mix different CONFIGURE_STYLE values. Iconic escape hatch behavior. 👑
  • MODQMAKE_install — same as for MODQMAKE_build, but used in the do-install stage. 🌈

🌟 SEE ALSO 🌟

That's the whole vibe, bestie! 🫶 This page's footer says source/version Debian, date November 27, 2022, and title QMAKE-MODULE(5). Mwah 💋

📦 where this page comes from