Skip to content

Force rebuild if DOKAN_DLL_OUTPUT_PATH is set but points to non-existing file #21

@madadam

Description

@madadam

If DOKAN_DLL_OUTPUT_PATH is set but the file it points to doesn't exists and the crate is otherwise considered fresh, the dll is not rebuilt.

One case where this is a problem is when cache is enabled on github CI: when there is a cache hit on the dokan-sys crate it's not rebuilt which means the dll is not placed to DOKAN_DLL_OUTPUT_PATH which causes the subsequent steps to fail, if they require the dll to be there.

The fix should be simple: add cargo::rerun-if-changed directive for the file at DOKAN_DLL_OUTPUT_PATH if the var is defined.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions