Fix bundling of the atf version into pkgconfig files and atf-version.

Sigh; one more attempt. This time I'm sure I've verified that the
.pc files contain the right number and that atf-version also outputs
the right stuff... Both with a clean and non-clean obj directory.

Should fix part of the problems reported in PR bin/48624.

Fix the bundling of the version number in built files.

Yes, attempting yet another fix at this so that the version number that
gets recorded in the pkgconfig files and inside atf-version really matches
the latest imported version. Should resolve issues where the built files
get stuck with an older version number during update builds.

This time, I'm trying the same approach I applied in the FreeBSD source
tree, which has been working fine so far across various release imports.

Homogenize reachover build file structure with that of kyua-cli:

- Move the majority of the common build definitions to the top-level
Makefile.inc and ensure this gets included everywhere.
- Move the bconfig.h file to the top-level directory.
- Add a statically-generated defs.h file instead of creating one
during the build. Easier to understand and less chances for things
to go wrong.
- Make sure all files using ATF_VERSION have the right dependency to
trigger a rebuild when the value changes.
- Clean up stale -I flags.

This is all mostly for simplicity reasons and to reduce the cognitive
load required to understand the build of the atf and kyua-* packages.

I have tested this with both MKKYUA=no/yes and non-clean/clean builds
so hopefully I got the details right. But if not, let me know please.

Deduce the version number to encode in pkgconfig files by getting it from
bconfig.h. Also make the build of these files depends on bconfig.h itself.

This should fix once and for all the problems of the
atf/atf-{c,c++}/pkg_config_test:version tests breaking because the
pkgconfig files hold an old version number during update builds.

Fix atf version in pkgconfig files (should be 0.17).

Keeping these files up to date with every new import is too easy to get
wrong. Would be nice if we'd extract the version number in some other
manner, like from lib/libatf-c/bconfig.h.

Found by martin@.

branches: 1.7.2;
Update reachover Makefiles for atf 0.16.

As part of this change (and as done upstream and in various packaging
systems), start shipping shared libraries of both libatf-c and libatf-c++.

Update reachover build files and scripts to deal with the just-imported
atf 0.15.

branches: 1.5.2;
Update reachover build files for atf-0.14.

branches: 1.4.2;
Set DPADD to point to the static versions of libatf-c and libatf-c++ as
appropriate.

branches: 1.3.2;
Adjust reachover makefiles for atf 0.11.

Update reachover makefiles for atf 0.10.

Adjust reachover makefiles for atf 0.9.

Sync with HEAD

Catchup with rmind-uvmplock merge.

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")

sync with head

sync with head

Rebase to HEAD as of a few days ago.

resync from head

resync with head