wx-config(1)

✨ wx-config — the wxWidgets configuration search & query tool, bestie edition 💅

okay so this is the manual page for wx-config, part of wxWidgets. She's a whole icon and she's about to tell you everything about the wxWidgets libraries chilling on your system. 🎀

---

🌸 SYNOPSIS

wx-config [ OPTIONS ... ] [ LIB ... ]

---

💖 DESCRIPTION

So basically, wx-config returns information about the wxWidgets libraries available on your system. That's it, that's the gig. You use it to grab all the info you need to build applications with those libraries. 🫶

Back in the day, if you wanted to change which library options your app used, you had to manage alternative configurations through some system-dependent means. 💀 Not anymore, bestie. Now you can select from any of the configurations installed on your system through this one single tool. Iconic behavior, honestly.

You can peep all the available configurations installed in the system default prefix with:

wx-config --list

…and then select from them using the feature options described below. Periodt.

Optional LIB arguments (comma or space separated, she's flexible ✨) may be used to specify individually the wxWidgets component libraries you want to use, or to specify additional components that aren't usually included by default. The magic token std may be used to import all the libraries that would be used by default if none were specified explicitly. Obsessed.

eg.

wx-config --libs std,gizmos

---

✨ OPTIONS ✨

wx-config accepts the following options with no restrictions on their order, unlike previous releases where order was a whole thing. We don't do that anymore. 🌈

🎀 Installed root

These options change or query the filesystem root for the operations listed below. Rootin' around, as one does. 🧚

• --prefix[=PREFIX] — Without the optional argument, the current default prefix gets output. If you do supply the argument, PREFIX will be searched for matching configs instead of the default. And yes, you may use both forms in the same command. Slay. 💜
• --exec-prefix[=EXEC-PREFIX] — Similar to --prefix, but she acts on the exec-prefix instead. If not specified, it defaults to the value of prefix. No cap.

🔍 Query options

These options return information about the wxWidgets default version and the installed alternatives. Info dump, but make it cute.

• --list — List all configs in prefix and show the ones that match any additional feature options you gave. 👑
• --release — Output the wxWidgets release number.
• --version-full — Output the wxWidgets version number in all its glory. 🌟
• --basename — Output the base name of the wxWidgets libraries.
• --selected-config — Output the signature of the selected wxWidgets library. This is a string of the form "port-unicode-version". iykyk 💅

🦋 Feature options

These options select features, which determine which wxWidgets configuration gets used. Vibe check for your build.

• --host=HOST — Specify a (POSIX extended) regex of host aliases to match for cross compiled configurations. eg. --host=i586-mingw32msvc, --host=.*. If unspecified, the default is to match only configurations native to the build machine. 🏠
• --toolkit=TOOLKIT — Specify a (POSIX extended) regex of the toolkits to match. The toolkit is responsible for the look and feel of the compiled application. eg. gtk, gtk2, motif, msw. If unspecified, the default is to prefer the system default toolkit, but to match any toolkit in the absence of a stricter specification. She's chill like that. 🌸
• --version[=VERSION] — Without the optional argument, return the wxWidgets version. If you supply the argument, it specifies a (POSIX extended) regex of the versions to match. If unspecified, the default is to prefer the system default version, but to match any version in the absence of a stricter specification. 🍓
• --unicode[=yes|no]] — Specify the default character type for the application. If unspecified, the system default will be preferred, but any type may match in the absence of a stricter specification. ✨
• --debug[=yes|no]] — Specify whether to create a debug or release build for the application. If unspecified, the system default (release) will be preferred, but any type may match in the absence of a stricter specification.

Debug versions are very useful for finding certain common ways of misusing the wxWidgets API, and you are encouraged to use them during active development of applications. They are not binary compatible with release versions, and packages built against wxWidgets debug builds should never be uploaded to Debian.

🚨 bestie this one matters: debug builds are not binary compatible with release builds, and you do NOT upload packages built against wxWidgets debug builds to Debian. Ever. Don't do it. 💀

• --static[=yes|no]] — Specify whether to statically or dynamically link wxWidgets libraries into your application. If unspecified, the system default (dynamic) will be preferred, but any type may match in the absence of a stricter specification. Static linking is mainly useful still for cross ports not natively supported by Debian, and can be hazardous in conjunction with the GTK toolkits. Note that static libraries are no longer included in the wxGTK packages.

⚠️ static + GTK toolkits = hazardous. And heads up: static libraries are no longer included in the wxGTK packages. 🫠

👑 Compiler options

These options generate the output required to build an application using a particular wxWidgets configuration. Main character energy for your build system. 🔥

• --libs — Output link flags required for a wxWidgets application.
• --cppflags — Output parameters required by the C preprocessor.
• --cflags — Output parameters required by the C compiler.
• --cxxflags — Output parameters required by the C++ compiler.
• --cc — Output the name of the C compiler $(CC).
• --cxx — Output the name of the C++ compiler $(CXX).
• --ld — Output the linker command.

---

💜 COPYRIGHT

This manpage was written by Ron Lee <ron@debian.org> for the Debian GNU/Linux distribution of wxWidgets. It may be freely distributed by anyone who finds it useful. 💖 (king behavior tbh, free to share, no gatekeeping 🫶)

---

and that's the whole page, bestie ✨ this one's from the Debian GNU/Linux era, dated 29 Sep 2004 — shoutout to the classics, they still ate 🌈🎀🦋