johnthagen/clion-cppcheck

Cppcheck should only be invoked with a single configuration

Open

#34 opened on Apr 9, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (7 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (37 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Environment

  • Operating System (e.g. Ubuntu 16.04 x64): Windows 10
  • IDE Version (e.g. CLion 2016.3.2): Clion 2020.1 (201.6668.86)
  • Cppcheck executable version (cppcheck --version): 1.90
  • Cppcheck plugin version: 1.4.2

Expected behaviour

The inspections show issues in active code only.

Actual behaviour

The inspection may should code in non-active (i.e. _MSC_VER although GCC is being used) blocks.

If Cppcheck is invoked with just a source file it tries to detect and process all configuration (i.e. defines) in the source. In case of the IDE it should only do a scan for that current configuration. This requires the plugin to get this from the IDE (if possible) and provide it to the call.

Contributor guide

Research direction
Investigate how to retrieve the current build configuration (defines, compiler) from CLion's project model and pass it to the cppcheck command line.
Tech stack
java
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaIntelliJ plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30