>>>> "Ville" == Ville Skytt <Ville>
writes:
Ville> I find using a *config program or a pkgconfig *.pc file
Ville> more future proof than that.
In theory, but the code I'm modifying basically goes back to 1999 IIRC
and still works for *finding* PostgreSQL. It's diagnosing the
additional libraries where it falls down. And as you point out,
pg_config doesn't do the --lib stuff that I'm working on. So tell me
again about future proofing when the technology has succeeded at least
once in the past. ;-)
Jokes aside, I'm all for portability. pkgconfig probably _does_ give
it by now, but none of the programs I hack configure for use it (I
think I was told about one exception, probably freetype, a couple of
months ago but haven't got around to picking up on that). All of the
ad hoc programs suffer from the same kind of problem that pg_config
does: they don't work in as many contexts as autoconf hackery does, so
you need to do the autoconf hackery anyway.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.