-
Notifications
You must be signed in to change notification settings - Fork 102
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
Change working directory of C++ parser #572
Open
andocz
wants to merge
11
commits into
Ericsson:master
Choose a base branch
from
andocz:cppparser-chdir
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
c46d0bb
Make C++ parser use the working directory of compilation commands
andocz 5e257ab
Don't make source file path absolute in ClangTool invocation
andocz ce956a8
Fix inaccuracies in SourceManager::getFile's comments
andocz 96345c4
Add PrefixingFileSystem that emulates chdir even for non-existent dirs
andocz 19cda25
Rename PrefixingFileSystem to FakeWorkDirFileSystem
andocz 581d2e9
Remove FakeWorkDirFileSystem
andocz cca922e
Save build directory in database
andocz 10de276
Use saved build directory when invoking Clang tool in reparser
andocz ecae845
Convert all path arguments to canonical in DatabaseFileSystem
andocz e0c6dba
If the build directory doesn't exist, use '/' and emit warning
andocz 03cb8e9
Fix segfault in PPIncludeCallback::InclusionDirective
andocz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
#ifndef CC_MODEL_BUILDDIRECTORY_H | ||
#define CC_MODEL_BUILDDIRECTORY_H | ||
|
||
#include <memory> | ||
|
||
#include <odb/core.hxx> | ||
|
||
#include <model/buildaction.h> | ||
#include <model/file.h> | ||
|
||
namespace cc | ||
{ | ||
namespace model | ||
{ | ||
|
||
struct BuildAction; | ||
|
||
#pragma db object | ||
struct BuildDirectory | ||
{ | ||
#pragma db id auto | ||
std::uint64_t id; | ||
|
||
#pragma db not_null | ||
std::string directory; | ||
|
||
#pragma db not_null | ||
#pragma db on_delete(cascade) | ||
std::shared_ptr<BuildAction> action; | ||
}; | ||
|
||
typedef std::shared_ptr<BuildDirectory> BuildDirectoryPtr; | ||
|
||
} // model | ||
} // cc | ||
|
||
#endif // CC_MODEL_BUILDDIRECTORY_H |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why this has to be a brand new table, foreign key, and all that jazz for the storage.
BuildAction
already containsstring command;
, for example. If"directory"
is just another member of the entries in a compilation database JSON (just like"command"
), then why isn't this reflected in the schema? Every build action MUST have a build directory (it just may or may not exist or point to anything meaningful).This struct, as it is now, won't do uniqueing of build directories either, because it is the build directory that refers to one build action each. If we want a separate record to only store one directory ("string") exactly once, then it is the buildaction that has to refer into this relation's key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to keep backwards compatibility with existing databases, that's why I didn't want to change
BuildAction
's schema. Is that not a priority? In that case you're right, storing it inBuildAction
would make more sense.Deduplicating the strings is not worth the hassle, in the CodeCompass SQLite database
BuildAction
only takes up 0.012% of the space.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can easily reparse projects, backward-compatibility with existing databases is not a high priority.