How to generate .pc file for a library?

Hi,
Generally, when installing a C /C++ library, is it possible to specify that generating its pc file is desired? If it is, how to specify? Will the directory of the pc file be added to PKG_CONFIG_PATH automatically? Thanks!

For example, I couldn't fetch info of libjpeg and libpng by using pkg_config:

"$ pkg-config --cflags --libs libjpeg
Package libjpeg was not found in the pkg-config search path.
Perhaps you should add the directory containing `libjpeg.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libjpeg' found"

"$ pkg-config --cflags --libs zlib
Package zlib was not found in the pkg-config search path.
Perhaps you should add the directory containing `zlib.pc'
to the PKG_CONFIG_PATH environment variable
No package 'zlib' found"

Thanks a lot!

.pc files aren't magical. They're not generated, they're written. (With some text substitutions at installation time to fill in the install path.) So if a library doesn't provide a .pc file, you can either write one yourself (it isn't hard - the pgk-config man-page explains it) or use some other way to find the location of the library. (Of course, writing your own .pc file isn't much use when distributing.)

zlib and libjpeg don't provide package config files.

Thanks!
If no pc files, what are the other possible ways to find the location of a given library?

There is none. If you have a configure script, do the standard thing: add a --with-zlib=/path/to/zlib option, and default to relying on standard include and library directories. Attempt to compile and link a test program. If it fails, tell the user. There's got to be existing macros for this.

Do you mean to specify where to install in the configure file?

No, to specify where the existing version was installed.

I think I still understand in a wrong way.

Since the library has already been installed and its configure file was only used during its installation, how can modifying its configure file will let users know what its files are and where they are by building a test C/C++ program that uses the library?

What is the purpose of "--with-libraryname" in the configure file of a library?

Thanks for clarification!

Quote:

---

Originally Posted by lehe

I think I still understand in a wrong way.

Since the library has already been installed and its configure file was only used during its installation, how can modifying its configure file will let users know what its files are and where they are by building a test C/C++ program that uses the library?

What is the purpose of "--with-libraryname" in the configure file of a library?

Thanks for clarification!

---

No, the configure file modifies the .pc file.

--with-libraryname tells configure that "libraryname" lives at a non-standard location.

--
Mats

After configure file is modified, how does the change in configure file take effect without reinstalling the library? I know I am wrong, but I think it is only used when calling "./configure" during installation. After installation, I can delete the whole package including configure file from where the library is built.

And how to get the information that --with-libraryname tells configure?

Quote:

---

Originally Posted by lehe

After configure file is modified, how does the change in configure file take effect without reinstalling the library? I know I am wrong, but I think it is only used when calling "./configure" during installation. After installation, I can delete the whole package including configure file from where the library is built.

And how to get the information that --with-libraryname tells configure?

---

That is correct. And the .pc file is generated DURING the build which is based on the ./configure run. You do not CHANGE configure - you change the .pc file.

Once the library file is installed, you can't move it (without changing the .pc file, at least).

--
Mats

I was talking about the configure file for your program.