Skip to content

Unnecessary Dependency on Clang/LLVM for Non-C/C++ Analysis #108

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

Closed
rahlk opened this issue Feb 20, 2025 · 0 comments · Fixed by #112
Closed

Unnecessary Dependency on Clang/LLVM for Non-C/C++ Analysis #108

rahlk opened this issue Feb 20, 2025 · 0 comments · Fixed by #112
Assignees
Labels
bug Something isn't working

Comments

@rahlk
Copy link
Collaborator

rahlk commented Feb 20, 2025

Description

Users are required to install brew install clang llvm even when they are not analyzing C/C++ code. This imposes an unnecessary dependency on LLVM/Clang for users working with other languages like Java or Python.

Steps to Reproduce

  • Set up the tool for analyzing a non-C/C++ project (e.g., Java, Python).
  • Attempt to run an analysis without installing Clang/LLVM.
  • The tool prompts users to install clang and llvm, even though these dependencies are not needed for non-C/C++ analyses.

Expected Behavior

  • The tool should not require clang and llvm unless analyzing C/C++ code.
  • Dependency checks should be conditional based on the selected language.

Suggested Fix

  • Update the installation requirements to make Clang/LLVM optional, only enforcing them when analyzing C/C++ projects.
  • Modify dependency validation logic to check the target language before prompting users to install Clang/LLVM.

Additional Context

N/A

@rahlk rahlk added the bug Something isn't working label Feb 20, 2025
@rahlk rahlk self-assigned this Feb 20, 2025
@rahlk rahlk linked a pull request Feb 21, 2025 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant