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

[Enrico Weigelt]

* Rich Felker <dalias at aerifal.cx> schrieb:

<snip>

> > Huh ! And how do you do cross compilation ?
> 
> Cross-compiling is a special case that you need to make lots 
> of preparations to deal with. 

Not as such. 99% of all my builds are cross-builds - for me
non-cross-compiling is a special case.
And most packages work quite good (at least w/ minor fixes).

> pkg-config will not magically solve your problem.

No, but an slightly modified one will do. You can easily plug 
in your own pkg-config which handles all your individual things,
without any change of the package's source code.

BTW: the current devel branch also supports sysroot.

<snip>
> > Also you didn't replied about dependencies. What if certain 
> > versions of libfoo requires you to add -lbar ?
> 
> For dynamic libraries, this is automatically taken care of. 

Maybe on ELF, but there're many other platforms, which dont't 
support that. 

You wanna drop support for all these platforms, just for satisfying
your personal fundamentalism ?

> For archive (static) libraries, one solution (perhaps the most 
> proper for strange dependencies) is including one archive inside 
> the other.

Bad hack, not an solution. And not the scope of the *importing* 
package (ie mplayer).

> However, for most common libraries, the dependencies are _known_ by
> the program using the library, e.g. libpng's dependence on libz.

Very bad design. (any design at all ?)

Why should someone using a certain library have to cope with 
(probably changing) implementation details of this library,
and of course its dependencies, too ?

<snip> 

> Seriously, this all worked fine for the past 7 years or so 
> before there was such a thing as pkg-config. 

Yeah, but with quite much handwork. And probably not for things
like (sysroot'ed) crosscompiling.

> pkg-config is yet another case of overengineering and inventing 
> a solution to a nonexistant problem, or rather inventing the
> problem itself, which seems to be a common mistake of GNU/Linux 
> these days and leads to endless bloat...

No, its an simple and efficient solution for an very common 
problem, which reduces the amount of necessary hand work.
Coders do not have to think about detecting the way to import
an certain anymore, instead just have to ask an database.
Distro maintainers are free to change it for their special 
needs, without having to touch the original packages.

I dont see whats problematic with that.


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