Explicit executable dependencies and cross-compilation

When packages use configure scripts, they usually have something like this:

rule
  (targets ...)
  (deps discover.exe)
  (action (run ./discover.exe)))

As of today, this does not work in a cross-compilation setting, because it adds a dependency towards config.exe in the cross-compiled workspace, which is not a good thing (and fails due to missing unix, usually).

My guess is that dune performs the following expansions:

• (deps discover.exe) -> (deps %{dep:discover.exe}) -- pointing to the cross-compiled workspace
• (run ./discover.exe) -> (run %{exe:./discover.exe}) -- pointing to the host workspace (as intended)

A simple workaround is to remove the explicit deps field towards executables, but that might seem counter-intuitive to some package maintainers so I was wondering if this behavior was intended. Thanks !

Using dune master branch and ocaml 4.11.1

The issue names no source files or tests. Start by reproducing the configure-script rule during cross-compilation and trace how explicit executable dependencies and (run ...) expressions are expanded. Done means the intended host-versus-target dependency behavior is established and covered by an appropriate regression test or documented clearly.