Exposing mock (ffi, hardware) bindings for test, doc, coding on another target

Looking for anyone who has tried this approach and can either provide a "won't work" or "good idea" experience. Background I'm currently working on a crate & app which (initially) targets windows and includes custom ffi bindings to provide hardware access.[1] I code on linux and cross-compile, while I can set up rust-analyzer to work with an alternative target, I'd also like to no-run rather than ignore doc-tests and ideally create & run unit tests. Idea I've just started to work out the foll...