-
Notifications
You must be signed in to change notification settings - Fork 385
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
Analyzer binary dependent environment #4305
Conversation
fa85919
to
43be7f0
Compare
If a pre-package analyzer binary (e.g. clang) is found first, the LD_LIBRARY_PATH must be extended. On the other hand, if the analyzer binary is taken from the users machine, the original environment must be used to execute the binary. This patch introduces an analyzer binary dependent environment initialization.
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.
SourceAnalyzer
class has a virtual function: analyze()
. This sets the environment accordingly. The inherited Gcc
and Cppcheck
classes override this function which also set the environment. I think, we shouldn't expect the child classes do this job. The analyze()
functions in these two inherited classes could be removed.
Co-authored-by: bruntib <bruntib@users.noreply.github.com>
Good point! Fixed! |
If a pre-package analyzer binary (e.g. clang) is found first, the LD_LIBRARY_PATH must be extended. On the other hand, if the analyzer binary is taken from the users machine, the original environment must be used to execute the binary.
This patch introduces an analyzer binary dependent environment initialization.