On Fri, 24 Jul 2026 at 01:09, Pierrick Bouvier <[email protected]> wrote: > > Now that we can link a single-binary with at least two targets (arm, aarch64), > we want to make sure that we expose the same set of machines (later devices > and > cpus) than target binaries. For that, we implemented a static filtering based > on > target interfaces that each machine will implement to declare which targets > have > this machine. > > However, we discovered that this static filtering is not enough. Indeed, some > machines and devices do not depend only on target, and their presence can > depend > on Kconfig or host/target combination. Thus, our static approach can't work, > and > we need something more flexible.
Do you have some specific examples of where the static filtering isn't sufficient? I can certainly believe that we have some at the moment, but I'm curious about how much of that is "just by accident because ifdefs were the easy thing to do" versus when the filtering makes sense for avoiding showing the user things that won't work. -- PMM
