Extensions to .pc files
bradh at frogmouth.net
Sat Jun 6 21:20:42 PDT 2009
I'd like to ask for an opinion on the best way to manage extensions to the
normal contents of a .pc file.
Conceptually, I'd like to be able to get back a path to a particular
configuration / script file, which I'm going to (optionally) add to my
command line to make the compiler do something different.
[The example here is dehydra, which is a static analysis tool from mozilla
if a library provides a set of checks as "libfoo-check.js", I'd like
pkg-config to be able to tell me if there is such a set of checks, and where
they can be found.]
I considered using the --variable command line option, but it seemed somehow
inconsistent to use it for this. Setting variables also uses a different
syntax, which isn't ideal:
The other possibility I considered (actually considered first, before I
realised I could use the --variable approach) was to extend pkg-config to use
a X.foo_extension syntax:
then we could use
$ pkg-config --x=dehydra_script foo
Thoughts or suggestions?
More information about the pkg-config