Hi Mark,
On 2025-06-09 17:42:47+0100, Mark Brown wrote:
> While running the nolibc tests I discovered that they build a kernel in
> the current directory, including overwriting the existing .config. This
> is rather suprising for the selftests build system - it usually wouldn't
> do a kernel build at all - and might be annoying for users.
This is not intended. I think a recent configuration change is broken [0].
The order-only dependencies don't work as I thought they would.
I'll rework this.
> KUnit deals with this by doing it's kernel build in a .kunit directory,
> it'd probably be good to do something similar for nolibc.
I assume you are using "make" directly. For a more complete
kunit.py-like solution we have run-tests.sh, which does indeed use a
dedicated build directory.
And maybe "soon" you get to use kunit directly to test nolibc.
[0] d7d271ec30dd ("selftests/nolibc: execute defconfig before other targets")
Thomas
