Skip to content

bins change on rebuild, even though there's no change in source code? #1229

@emiltin

Description

@emiltin

i'm working on smarter caching of test files, so that extracting and preparing will not be run if only the osrm-routed binary changed.

but it seems that relinking will change the bins even though no source code has changed. somehow linking must involve a timestamp or random number? after running 'rake' from the root folder, all the bins have new a new sha1sum, which makes it impossible to skip the extraction/preparing step.

running osrm-extract -v shows the same version string; the git revision is unchanged, and there's no data info. so it must be something else.

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