Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-build gst-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-buildgst-build
  • Issues
  • #85

Closed
Open
Created Mar 11, 2020 by Vivia Nikolaidou@vivia🦆Maintainer

Running ninja with no changes reconfigures meson

Using gst-build git and meson git, also have configured meson to also compile gst-plugins-rs. Every time I rerun ninja, it reconfigures meson.

$ ninja -d explain -n
ninja explain: output build.ninja older than most recent input ../build/subprojects/gst-plugins-rs/libgstrsaudiofx.so (1583938874736613098 vs 1583938876648647571)
[0/1] Regenerating build files.

Taking a second look, looks like all files in build/subprojects/gst-plugins-rs/ are regenerated (or at least their mtime is updated) every time cargo is run without changes.

Reverting 7cf00627 fixes it (thanks to @seungha.yang for bisecting).

Assignee
Assign to
Time tracking