如何确定pkg-config所需的库名称？专家如何解决这类难题？

Great question—this is such a common pain point, and no, none of us have all the library names memorized! I’ve definitely struggled with this exact issue with libraries like DLIB too. Here’s how I (and most folks in the dev community) figure it out:

• Locate the .pc file directly
  pkg-config relies entirely on .pc configuration files to recognize libraries. These files are usually stored in standard paths like /usr/lib/pkgconfig, /usr/local/lib/pkgconfig, or sometimes /usr/share/pkgconfig. Use find to hunt for the file related to your library:

  find /usr/lib/pkgconfig /usr/local/lib/pkgconfig -name "*.pc" | grep -i dlib
  

  The name of the .pc file (without the .pc extension) is exactly what you need to pass to pkg-config. For example, if you find dlib-19.9.pc, then pkg-config --cflags dlib-19.9 would work. If you don’t find any .pc files, that’s a clue you might be missing the development package for the library—on Debian/Ubuntu systems, this is usually something like libdlib-dev (install it with sudo apt install libdlib-dev).

• Check for a library-specific config tool
  Many libraries ship their own configuration scripts instead of (or in addition to) pkg-config support. For DLIB, try running:

  dlib-config --cflags --libs
  

  This will spit out the exact compiler and linker flags you need, no pkg-config required. Tools like this are often named [library]-config, so it’s worth trying that pattern.

• Use your package manager to trace the .pc file
  If you’re on a system with a package manager (like apt, dnf, or brew), you can search for which package provides the .pc file. For example, on Ubuntu:

  apt-file search dlib.pc
  

  This will tell you which package includes the pkg-config file, and confirm the correct name you should use.

• Don’t rely on ldconfig output alone
  The ldconfig -p command shows you shared libraries available at runtime, but pkg-config uses the development metadata (the .pc files) which are part of the dev package. These are often separate, so the .so filename doesn’t always map directly to the pkg-config library name.

At the end of the day, it’s all about knowing where to look for the metadata, not memorizing every possible library name.

内容的提问来源于stack exchange，提问作者puk