Skip to content

[WIP] Regenerate the compilation database only if the content has changed #3735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[WIP] Regenerate the compilation database only if the content has changed #3735

wants to merge 2 commits into from

Conversation

exg
Copy link

@exg exg commented Jul 5, 2020

Contributor Checklist:

  • I have created a new test or updated the unit tests to cover the new/changed functionality.
  • I have updated CHANGES.txt (and read the README.rst)
  • I have updated the appropriate documentation

exg added 2 commits July 5, 2020 17:09
@exg
compilation_db: test db regeneration on compile command change
eb669cb 
This commit adds a dummy '-g' option to the fake gcc so as to be able
to modify a compile command by adding flags.
@exg
compilation_db: regenerate the db only if the content has changed
5f07d12
@exg exg force-pushed the compilation-db branch from 1fdfb3a to 5f07d12 Compare July 6, 2020 09:12
@bdbaddog bdbaddog added the clang clang support label Aug 2, 2020
@mwichmann mwichmann added this to 4.10 Apr 10, 2025
@mwichmann mwichmann moved this to Backlog in 4.10 Apr 10, 2025
@mwichmann mwichmann removed this from 4.10 Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
clang clang support
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@exg @bdbaddog