[MPlayer-dev-eng] [PATCH] directfb -> pkg-config

Enrico Weigelt weigelt at metux.de
Mon Feb 20 20:43:09 CET 2006


* The Wanderer <inverseparadox at comcast.net> schrieb:

<snip>

> And what about cases where the program using the library does *not* know
> about the dependencies? It is entirely conceivable, given some of my
> back-burner projects, that I might have one day attempted to write a
> program capable of producing PNG output; I had no idea that libpng
> depended on libz. When initial compile tests gave linker errors,
> pkg-config is the first thing I would have thought of (other than random
> Googling) to try to find out what compiler flags I would need in order
> to successfully compile such a program.

Right. And that's exactly how you should do your build at all.
One day the depencies may change, and all packages (going this 
naive way) have to be fixed again. And its getting even worse:
they have to explicitly check the version of imported libraries
and handle depencies different on the library version.

I personally dont see any reason for that if it can be so easy.

<snip>

> I'm not saying "we should use pkg-config exclusively and dump 
> the current system used in configure"; 

Well, we could do it, without hurting people like Rich, having
no pkg-config themselves:

We could simply write our own pkg-config replacement, which just
contains the current tests and simply supplies an compatible 
command line interface. By default (aka $PKG_CONFIG is not set, 
and maybe /usr/bin/pkg-config not existing) this script is used. 


cu
-- 
"*Who am I*? I am Susan Ivanova, Commander, daughter of Andrei and Sophie
  Ivanova. I am the right hand of vengeance, and the boot that is going 
  to kick your sorry ass all the way back to Earth... I am Death Incarnate, 
  and the last living thing that you are ever going to see. God sent me."
                                                       -- Cmdr. Ivanova




More information about the MPlayer-dev-eng mailing list