On Mon, Dec 11, 2023 at 12:29:58PM -0800, John Hubbard wrote: > On 12/11/23 12:21, Mark Brown wrote: > > additional variables that depend on the user's build environment, we > > already have enough build issues. It ought to be mostly tedious rather > > than hard but it's still a pain, especially given the issues we have > > getting kselftest fixes merged promptly. > What about David's option (3): > (3) Regularly archive the required headers in the selftest directory > like external projects like QEMU do. > , combined with something in the build system to connect it up for > building the selftests? > Or maybe there is an innovative way to do all of this, that we have > yet to think of. We do copy files into tools/include at random times which makes sense for things that aren't uapi, and we are putting bits of uapi there already so we could just expand the set of files copied there. AFAICT the only reason we're copying the uapi files at all is that they're directly in the same include/ directories as everything else and are always referenced with their uapi/ prefix.
Attachment:
signature.asc
Description: PGP signature
