"Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost> writes: > Am Sat, 08 May 2021 10:08:35 -0400 > schrieb Greg Troxel <gdt%lexort.com@localhost>: > >> "Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost> writes: >> >> > One could check for these two, but that would mean two calls to >> > pkg-config for each bmake run. Sadly, I don't see an equivalent to >> >> I don't follow "each bmake run". If this cost is incurred when actually >> building pkgconf, and not otherwise, that seems fine. > > Duh, you're right. I was thinking about including this in a platform mk > file, but yes, this stuff should only go into the pkgconf and > pkg-config Makefiles. > > So … what do you think about these crude ways of extracting the search > paths? Probably best put into an auxilliary script in files/. If it's conditioned on something in platform.mk that says there is (maybe) native pkgconf, and doesn't break anything on other platforms, seems a bit icky but I don't have any better ideas. Maybe someone else does.
Description: PGP signature