Vcpkg: pkgconfig subdirectory in installed/x64-linux/lib

[crusader-mike]

Some projects (zstd/xerces-c/etc) put .pc files into installed/x64-linux/lib/pkgconfig and installed/x64-linux/debug/lib/pkgconfig.

What is the purpose of these files? Do they have to be removed during port install? Why they get generated in two places?

[Voskrese]

https://www.google.com/search?client=firefox-b-d&q=pkgconfig

[crusader-mike]

@Voskrese, huh... I've never heard of this "google" service. It looks useful. Thanks! :-)

I asked because port isn't supposed to generate shared directory in debug (validation fails), but having pkgconfig in two places doesn't trigger validation logic. Was curious for reasons why.

[Voskrese]

windows !

vcpkg\installed\x64-windows\bin>pkg-config --variable pc_path pkg-config

../lib/pkgconfig;../share/pkgconfig

pkg-config --libs --cflags glib-2.0

-IE:/tools/vcpkg/installed/x64-windows/bin/../include/glib-2.0 -IE:/tools/vcpkg/installed/x64-windows/bin/../lib/glib-2.0/include -lintl -LE:/tools/vcpkg/installed/x64-windows/bin/../lib -lglib-2.0

prefix=

prefix=E:/tools/vcpkg/packages/libtins_x64-windows
prefix=E:/tools/vcpkg/installed/x64-windows
On windows, the prefix is automagically build from the location of the .pc file
prefix=C:/dir_placeholder

vcpkg\installed\x64-windows\lib\pkgconfig\ glib-2.0.pc

prefix=E:/tools/vcpkg/installed/x64-windows
exec_prefix=${prefix}
libdir=${prefix}/lib
bindir=${prefix}/bin
datarootdir=${prefix}/share
datadir=${datarootdir}
toolsdir=${prefix}/bin
includedir=${prefix}/include

bindir=${prefix}/bin

glib_genmarshal=${bindir}/glib-genmarshal
gobject_query=${bindir}/gobject-query
glib_mkenums=${bindir}/glib-mkenums

Name: GLib
Description: C Utility Library
Version: 2.60.4
Libs: -lintl -L${libdir} -lglib-2.0
Libs.private: -lws2_32 -lwinmm
Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include

https://www.google.com/search?client=firefox-b-d&q=pkgconfig
-->>
https://www.freedesktop.org/wiki/Software/pkg-config/
-->>
https://people.freedesktop.org/~dbn/pkg-config-guide.html#faq

example

-Dpkg_config_path=${CURRENT_INSTALLED_DIR}/debug/lib/pkgconfig,${CURRENT_INSTALLED_DIR}/debug/share/pkgconfig

set(ENV{PKG_CONFIG_PATH} "${CURRENT_INSTALLED_DIR}/lib/pkgconfig/${_SEP}${PKG_CONFIG_PATH}")

what exactly in the official documentation is not clear?

[crusader-mike]

I see... Thanks!

what exactly in the official documentation is not clear?

I am still in the middle of reading it, but once am I done -- I'll send you a list of questions. ;-)