KF5-CONFIG(1)

πŸ’– KF5-CONFIG(1) πŸ’–

okay bestie, so this is the manual page for kf5-config β€” it lives in the kf5-config User's Manual section of your man pages, and it's literally your little tour guide for finding out where all your Frameworks stuff is hiding on your machine. let's get into it πŸ¦‹


✨ NAME ✨

kf5-config β€” prints Qt(TM) and Frameworks installation paths. that's the whole job. it's giving "where is everything" and honestly? we love a tool that just tells you. πŸ‘‘


✨ SYNOPSIS ✨

kf5-config [--expandvars] [--prefix] [--exec-prefix] [--libsuffix]
           [--localprefix] [--version] [--kde-version] [--types]
           [--path type] [--userpath type] [--install type]
           [--qt-prefix] [--qt-binaries] [--qt-libraries] [--qt-plugins]

like, no subcommands, no drama, just vibes and flags. pick your flag, get your answer. πŸ’…


✨ DESCRIPTION ✨

so kf5-config is a command line program you run to retrieve information about Frameworks installation paths, or about your user paths. that's it, that's the whole personality. πŸŽ€

use this program when you need to figure out where the various aspects of the Frameworks installation actually reside on your system β€” like, physically. on disk. the real location. no cap.

⚠️ note bestie, this one matters: kf5-config is mostly a deprecated replacement for kde4-config, and the recommended tool to use instead is qtpaths (which is shipped with Qt(TM)). so it still works, it's still here, but it's lowkey the old way. if you're starting fresh, qtpaths is the moment. 🫢

✨ OPTIONS ✨

one bullet per flag, no skipping, we're doing all of them because we respect the craft. 🌸

  • --expandvars β€” expands ${prefix} and ${exec_prefix} in the output. it takes those placeholder-y variables and actually spells them out for you. ✨
  • --prefix β€” the compiled in prefix for Frameworks libraries.
  • --exec-prefix β€” the compiled in exec_prefix for Frameworks libraries.
  • --libsuffix β€” the compiled in library path suffix.
  • --localprefix β€” the prefix in $HOME used to write files.
  • --version β€” the version of Qt(TM), plus the compiled in version string for Frameworks libraries and kf5-config. a little combo platter. πŸ“
  • --kde-version β€” the compiled in version string for Frameworks libraries.
  • --types β€” prints a list of all available KDE resource types. the whole roster. πŸ’œ
  • --path type β€” the search path for the specified type.
  • --userpath type β€” the user paths for the types: desktop|document.
  • --install type β€” the prefix to install resource files to.
  • --qt-prefix β€” the installation prefix for Qt(TM).
  • --qt-binaries β€” the location of installed Qt(TM) binaries.
  • --qt-libraries β€” the location of installed Qt(TM) libraries.
  • --qt-plugins β€” the location of installed Qt(TM) plugins. πŸ”₯

✨ EXAMPLES ✨

% kf5-config --prefix
% kf5-config --types
% kf5-config --path wallpaper

see? one flag, one answer, zero chaos. iconic behaviour fr fr. 🧚


✨ SEE ALSO ✨

  • kf5options(7) β€” go read that one too bestie, iykyk πŸ’–

✨ BUGS ✨

None known. not a single one. we're flawless, we're unbothered, we're bug-free (allegedly). πŸ’€βœ¨


✨ AUTHOR ✨

Stephan Kulow <coolo@kde.org>

  • Author. 🫑 thank you for your service king

and that's the whole page!! 🌈 this little slice of the docs came to you courtesy of KDE Frameworks Frameworks 5.13, dated 2015-07-31, and it's page KF5-CONFIG(1) of the kf5-config User's Manual. go forth and locate your paths, bestie πŸ’…πŸ‘‘