You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find winmd files without reading PATH nor copying to target/
Non-Windows platforms - which are supported for cross-compiling - do not
set the output directory in `PATH` nor use semicolons to separate this
variable, resulting in errors
Split out `winmd` "discovery" by emitting the path to these files in a
build step, that is subsequently compiled into `windows_gen`. This is
more efficient than `include_bytes!` which was used prior to the `PATH`
system as no copies or binary includes are required at all.
Copying of DLL targets to the `target/` dir for easy consumption and
running of crates is still performed, but only on Windows for the same
`PATH` reason.
In the future, if a chain of crates is required to export `winmd` files
for downstream crates to consume, this can be extended to also export
their `$CARGO_MANIFEST_DIR/.winmd/windows` in such a way that the next
crate can pick it up, again without copying any files around.
0 commit comments