On Sun, 17 Apr 2011 23:30:34 +0200 Tollef Fog Heen <tfheen@err.no> wrote: > ]] Reinhard Tartler > > | Neil, thank you very much for your insightful summary of the matter. Now > | it seems pretty clear that this issue cannot be handled in the libav > | package, but needs to be solved at the pkg-config level. I'm therefore > | reassigning this bug to pkg-config. > > Just to make it clear, what you want is a way for a package (libA) to > say «you can't build this statically»? If so, there's no way to do that > with pkg-config and unless you can convince me what the use case is and > why this is worth supporting, I'm not going to add it. Perhaps a little statement in pkg-config (1) in the section on --static which makes it clear that pkg-config (just as with the default '--dynamic' output) does not check this data and whether it works or not is undetermined? "Not all libraries support static linking and some libraries may still require other steps to allow programs to statically link using the output of pkg-config --static." Maybe also a statement in the main description that pkg-config does not (cannot) check whether the data in the .pc file(s) will actually allow programs to link against the libraries specified. That is the job of the build system using pkg-config. pkg-config is, after all, a config tool, not a QA or checking tool. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpjkFYkWiPBR.pgp
Description: PGP signature