PPKG-CONFIG(1)
π PPKG-CONFIG(1) π
From the User Contributed Perl Documentation, bestie β¨
β¨ NAME β¨
PkgConfig β Pure-Perl Core-Only replacement for pkg-config. Periodt. π
πΈ SYNOPSIS πΈ
π« As a replacement for pkg-config π«
This is the whole vibe: π¦
$ ppkg-config --libs --cflags --static gio-2.0
#outputs (lines artificially broken up for readability):
# -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
# -pthread -lgio-2.0 -lz -lresolv -lgobject-2.0
# -lgmodule-2.0 -ldl -lgthread-2.0 -pthread -lrt -lglib-2.0
pkg-config.pl can be used as an alias for ppkg-config on platforms that support it. It can also be installed as pkg-config though this is not recommended if your system has a native pkg-config.
Real talk: installing it aspkg-configis not recommended if your system already has a nativepkg-config. π
Compare to:
$ pkg-config --libs --cflags --static gio-2.0
#outputs ( "" ):
# -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
# -pthread -lgio-2.0 -lz -lresolv -lgobject-2.0 -lgmodule-2.0
# -ldl -lgthread-2.0 -lrt -lglib-2.0
π«Ά From another Perl module π«Ά
Look at this little icon: π
use PkgConfig;
my $o = PkgConfig->find('gio');
if($o->errmsg) {
#handle error
} else {
my $prefix = $o->get_var('prefix');
my @cflags = $o->get_cflags;
my @ldflags = $o->get_ldflags;
}
π DESCRIPTION π
PkgConfig provides a pure-perl, core-only replacement for the pkg-config utility. No cap, that's the whole point. π
This is not a description of the uses of pkg-config but rather a description of the differences between the C version and the Perl one.
While pkg-config is a compiled binary linked with glib, the pure-perl version has no such requirement, and will run wherever Perl ( >= 5.6 ) does. It's giving portable main character energy. π§
The main supported options are the common --libs, --cflags, --static, --exists and --modversion.
π SCRIPT OPTIONS π
π¦ USAGE π¦
<packagename1 pkgname2..> [ --options ]
π ARGUMENTS π
By default, a library name must be supplied unless one of --version, or --real-version is specified.
The output should normally be suitable for passing to your favorite compiler. Compiler girlies, this one's for you. π
--libsβ (Also) print linker flags. Dependencies are traverse in order. Top-level dependencies will appear earlier in the command line than bottom-level dependencies.--libs-only-Lβ Prints the-L/-Rpart of--libs. It defines library search path but without libraries to link with.--libs-only-lβ Prints the-lpart of--libs.--libs-only-otherβ Prints the part of--libsnot covered by--libs-only-Land--libs-only-l, such as--pthread.--list-allβ List all know packages.--cflagsβ (Also) print compiler and C preprocessor flags.--cflags-only-Iβ Prints the-Ipart of--cflags.--cflags-only-otherβ Prints the parts of--cflagsnot covered by--cflags-only-I.--modversionβ Print the version of a given package.--staticβ Use extra dependencies and libraries if linking against a static version of the requested library.--existsβ Return success (0) if the package exists in the search path.--with-path=PATHβ PrependPATHto the list of search paths containing.pcfiles.
This option can be specified multiple times with different paths, and they will all be added. Stack 'em, bestie. π
--env-onlyβ Using this option, only paths specified inPKG_CONFIG_PATHare recognized and any hard-coded defaults are ignored.--guess-pathsβ Invokegccandldto determine default linker and include paths. Default paths will be excluded from explicit-Land-Iflags.--define-variable=VARIABLE=VALUEβ Define a variable, overriding any such variable definition in the.pcfile, and allowing your value to interpolate with subsequent uses.--variable=VARIABLEβ This returns the value of a variable defined in a package's.pcfile.--print-variablesβ Print all defined variables found in the.pcfiles.--versionβ The target version ofpkg-configemulated by this script.--real-versionβ The actual version of this script.--debugβ Print debugging information.--silence-errorsβ Turn off errors. This is the default for non-libs/cflag/modversion arguments.--print-errorsβ Print errors to STDERR and takes precedence over--silence-errors.--short-errorsβ Ignored, but recognized for compatibility.--errors-to-stdoutβ Print errors to STDOUT and takes precedence over--print-errors.
π ENVIRONMENT π
The PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR variables are honored and used as a colon-delimited (semicolon-delimited on Windows) list of directories with contain .pc files.
Other environment variables recognized by both pkg-config and PkgConfig include:
PKG_CONFIG_ALLOW_SYSTEM_CFLAGSPKG_CONFIG_ALLOW_SYSTEM_LIBS
If Win32API::Registry is installed, on Windows (but not Cygwin) PkgConfig will also consult these registry keys. The names are ignored, but the values are paths containing .pc files.
HKEY_CURRENT_USER\Software\pkgconfig\PKG_CONFIG_PATHHKEY_LOCAL_MACHINE\Software\pkgconfig\PKG_CONFIG_PATH
Registry support should be considered somewhat experimental, subject to change in the future, though not without good reason. The rationale for this caveat is that this feature is documented in several places, but I have yet to find a working version that implements this feature. iykyk π
π MODULE OPTIONS π
π« PkgConfig->find π«
my $result = PkgConfig->find($library, %options);
Find a library and return a result object. $library can be either a single name of a library, or a reference to an array of library names.
The options are in the form of hash keys and values, and the following are recognized:
search_pathβ Prepend search paths in addition to the paths specified in$ENV{PKG_CONFIG_PATH}. The value is an array reference.search_path_overrideβ The_overridevariant ignores defaults (likePKG_CONFIG_PATH).file_pathβ Specifies the full path of the.pcfile that you wish to load. It does not need to be in the search path (although any dependencies will need to be). Useful if you know the full path of the exact.pcfile that you want.exclude_cflags,exclude_ldflags,exclude_cflags_override,exclude_ldflags_overrideβ Some.pcfiles specify default compiler and linker search paths, e.g.-I/usr/include -L/usr/lib. Specifying them on the command line can be problematic as it drastically changes the search order.
The above options will either append or replace the options which are excluded and filtered.
The default excluded linker and compiler options can be obtained via @PkgConfig::DEFAULT_EXCLUDE_LFLAGS and @PkgConfig::DEFAULT_EXCLUDE_CFLAGS, respectively.
staticβ Also specify static libraries.no_recurseβ Do not recurse dependencies. This is useful for just doing version checks.VARSβ Define a hashref of variables to override any variable definitions within the.pcfiles. This is equivalent to the--define-variablecommand-line option.
A PkgConfig object is returned and may be queried about the results:
$o->errmsgβ An error message, if any. This is a string and indicates an error.$o->pkg_existsβ Boolean value, true if the package exists.$o->pkg_versionβ The version of the package.$o->get_cflags,$o->get_ldflagsβ Returns compiler and linker flags, respectively.
In list context, these methods return a list with each argument split on unescaped spaces.
In list context returns a list of compiler and linker flags, respectively.
In scalar context returns a string of compiler and linker flags with spaces and quotes escaped correctly.
$o->get_var($name)β Get the variable with the given name.
π PkgConfig->Guess π
This is a class method, and will replace the hard-coded default linker and include paths with those discovered by invoking ld(1) and cpp(1).
Currently this only works with GCC-supplied ld and GNU ld. Lowkey niche, but slay. π
π INSTALL π
The Makefile.PL that comes with PkgConfig can take one or more --script options to change of the name of the script or scripts that are installed.
--script ppkg-configβ This is the default and works on all platforms.--script pkg-config.plβ This is installed by default on all platforms except for Windows, where the.plmay confuse the shell and cause the script to be opened in a text editor.--script pkg-configβ This is the default name of the realpkg-configand so you have to specifically enable it if you want it.--script noneβ Don't install any scripts.
Example, install all script names:
% perl Makefile.PL --script ppkg-config --script pkg-config.pl --script pkg-config
Example, don't install any scripts:
% perl Makefile.PL --script none
You can also set the environment variable PERL_PKG_CONFIG_SCRIPTS to the desired --script value (separating each script name with a comma ",") to ensure that upgrades of PkgConfig do the same. Future-proofing, bestie. π«Ά
π CAVEATS π
On Strawberry Perl ppkg-config acts like Strawberry is the system. This means that
- The
.pcfiles that are bundled with Strawberry are searched by default. - The Strawberry include and lib directories are used to compute the exclusion lists.
As of Strawberry 5.20.0.1 PkgConfig is bundled with Strawberry and pkg-config is installed by default (in addition to ppkg-config, though the ppkg-config alias is NOT bundled with Strawberry itself). Not me clocking that detail. π
For details on how to patch the .pc files bundled with older Strawberries, see the README.win32 that comes with this Distribution.
π BUGS π
The order of the flags is not exactly matching to that of pkg-config. From my own observation, it seems this module does a better job, but I might be wrong. ngl, iconic confidence. π
Unlike pkg-config, the scripts --exists function will return nonzero if a package or any of its dependencies are missing. This differs from the behavior of pkg-config which will just check for the definition of the package itself (without dependencies). fr fr, that's the tea. π
π SEE ALSO π
okay bestie, if you wanna go down the whole rabbit hole, here's the friend group β every single one of these is a real reference from the page:
pkg-configβ the original C implementation, living at<http://www.freedesktop.org/wiki/Software/pkg-config>πpkgconfβ an alternative C implementation, hanging out at<https://github.com/pkgconf/pkgconf>β¨PkgConfig::LibPkgConfβ Perl bindings forlibpkgconf, and yes it's literally the same library thatpkgconfis built on πExtUtils::PkgConfigβ a wrapper around thepkg-configbinary that you can use in yourMakefile.PLorBuild.PLπ¦<http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/pkg-config/>β another perl implementation of pkg-config πΈpkg-configβ<https://github.com/ruby-gnome2/pkg-config>β this one's the pure Ruby implementation πpykg-configβ<https://pypi.python.org/pypi/pykg-config/1.2.0>β a Python implementation π
π AUTHOR π
respect where it's due, bestie:
- Original Author:
M. Nunberg - Current maintainer:
Graham Ollis <plicease@cpan.org>
Other contributors include:
Vladimir Timofeev (vovkasm)kmxSanel ZukanBreno G. de Oliveira (garu)Gregor HerrmannIlya Pavlov (ILUX, Ilya33)Shawn Laffan (SLAFFAN, shawnlaffan)Ari Jolma (AJOLMA)
π COPYRIGHT AND LICENSE π
Copyright (C) 2012 M. Nunberg
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
mwah π this page is from perl v5.42.0, dated 2020-11-12, and it's literally PPKG-CONFIG(1). periodt. π«Ά
π¦ where this page comes from
- opensuse-leap 16.0: perl-PkgConfig 0.25026-bp160.1.11 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-PkgConfig 0.25026-bp160.1.11 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-PkgConfig 0.25026-bp160.1.11 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-PkgConfig 0.25026-bp160.1.11 Β· Artistic-1.0 OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms