-
Notifications
You must be signed in to change notification settings - Fork 23
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.
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
implement features #9
Comments
Converting file paths relative <-> absolute, why not, but I'm curious, what use case do you have in mind? To filter duplicate entries, there is something already, but it's nothing smart, it just outputs one compile command per file:
Filtering compilation commands arguments would be nice, but I'm wondering if/when I will get to it. Excluding files with pattern, is something I'd like very much, for the reason you mentioned. |
@Sarcasm In general, custom tools written with libASTMatchers and libTooling have a problem dealing with files that are compiled from different directories. Specifically, when
|
I've just hit upon another use case for the absolute→relative paths conversion. In a CI environment, I generate the compilation database from In many cases it's not really feasible to ensure that all the containers manipulate the project at the exact same path, because different containers might require you to mount your stuff into different places. |
Hey Guillaume, nice tool you've wrote. I was wondering that what's your opinion to implement these compilation database manipulations?
(Paths can be in
directory
andfile
, but also in thecommand
arguments too. Like-I/path/to/include
or-o /path/to/output
.)(Duplicates could be when the
directory
andfile
, but thecommand
has minor irrelevant differences like-MD
or-static
which are either preprocessing or linking flags. That's where the flag filtering could help.)(Some project contains dependency code, which they might not want to run the tooling against.)
The text was updated successfully, but these errors were encountered: