about summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorK900 <me@0upti.me>2023-01-03 15:39:40 +0300
committerK900 <me@0upti.me>2023-01-12 20:51:24 +0300
commitbf5a65096c94da69551d8b8f6274385eba062e35 (patch)
treeb5dbf8b298ecd2ad0208a34a20ba01f20a01f81a /doc
parent8f48e1cadbacb530571d969e07233aef68908cf0 (diff)
pkgs/all-packages: remove unused alias, add comment
Diffstat (limited to 'doc')
-rw-r--r--doc/languages-frameworks/qt.section.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/languages-frameworks/qt.section.md b/doc/languages-frameworks/qt.section.md
index 696031268ed91..e09194e391e1c 100644
--- a/doc/languages-frameworks/qt.section.md
+++ b/doc/languages-frameworks/qt.section.md
@@ -3,8 +3,10 @@
 Writing Nix expressions for Qt libraries and applications is largely similar as for other C++ software.
 This section assumes some knowledge of the latter.
 
-However, Qt makes extensive use of runtime dependency detection.
-In nixpkgs, those runtime dependencies are made into build dependencies through wrappers.
+The major caveat with Qt applications is that Qt uses a plugin system to load additional modules at runtime,
+from a list of well-known locations. In Nixpkgs, we patch QtCore to instead use an environment variable,
+and wrap Qt applications to set it to the right paths. This effectively makes the runtime dependencies
+pure and explicit at build-time, at the cost of introducing an extra indirection.
 
 ## Nix expression for a Qt package (default.nix) {#qt-default-nix}