Skip to content

mir/format.d triggers recompilation with meson/ninja #392

@Panke

Description

@Panke

I am using mir as a submodule in a meson project and build it with ninja. This happens to me every time I run ninja:

ninja -d explain
ninja explain: output mir/format.d of phony edge with no inputs doesn't exist
ninja explain: mir/format.d is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1.p/source_mir_exception.d.o is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1 is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1 is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1.p/libmir-core.so.1.1.1.symbols is dirty
ninja explain: subprojects/mir-algorithm/libmir-algorithm.so.3.7.0 is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1.p/libmir-core.so.1.1.1.symbols is dirty
ninja explain: subprojects/mir-cpuid/libmir-cpuid.so.1.2.3 is dirty
ninja explain: subprojects/mir-algorithm/libmir-algorithm.so.3.7.0 is dirty
ninja explain: subprojects/mir-algorithm/libmir-algorithm.so.3.7.0.p/libmir-algorithm.so.3.7.0.symbols is dirty
ninja explain: subprojects/mir-core/libmir-core.so.1.1.1.p/libmir-core.so.1.1.1.symbols is dirty
ninja explain: subprojects/mir-cpuid/libmir-cpuid.so.1.2.3 is dirty
ninja explain: subprojects/mir-cpuid/libmir-cpuid.so.1.2.3.p/libmir-cpuid.so.1.2.3.symbols is dirty
ninja explain: subprojects/mir-ion/libmir-ion.so.0.0.0 is dirty

There is a format.d in mir.algorithm, but that one obviously exists.

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