[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: no .pc file
Re: no .pc file
Fri, 26 Oct 2012 13:27:32 -0500 (CDT)
Alpine 2.01 (GSO 1266 2009-07-14)
On Fri, 26 Oct 2012, Yaroslav Bulatov wrote:
Oops my bad....that was a bad paste from some auto-generated code.
This is basically a modified version of .pc file I get when building
zlib. Not sure how useful this is because you need to update "prefix"
in this file manually each time you rebuild libtool. Ideally the .pc
file would be generated automatically by configure/make
If it is not clear, package config files are operating system and/or
operating system distribution and/or operating system release version
specific. One reason for this is that each operating system
distribution uses its own names for pkg-config package definitions.
Using zlib as an example is not useful since zlib does not depend on
any other packages. Most packages depend on other packages and so
there is an OS-distribution (or even site-specific) list of packages
that this package depends on.
While many packages do produce sample pkg-config files (based on
guess-work or assumption of a partiticular OS distribuiton), it is
common practice for the default offering to be modified by the OS
package distribution maintainer because the OS uses a different name
for a similar thing.
Being intended for portable software, libtool does not concern itself
with a hand-edited/non-portable framework like pkg-config.
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/