purgedConfiguration

2014-11-10
2017-02-01
  • Chris Saunders

    Chris Saunders - 2014-11-10

    I've tested the 1.67 release and have many new info messages following the pattern:

    "The configuration '" + configuration + "' was not checked because its code equals another one.",

    But can't figure out what the trigger criteria are for the subset of pre-processor symbols in our code that trigger this. Is there any additional documentation?

    Thanks!

     
  • Daniel Marjamäki

    It's not a problem. You don't need to fix this.

    Maybe Cppcheck should write which other configuration matches.

    But can't figure out what the trigger criteria are

    This message is written if configuration X generates the same preprocessor output as configuration Y. Then Cppcheck only checks either X or Y not both. This saves CPU and gives you the same results.

     
    Last edit: Daniel Marjamäki 2014-11-11
    • Chris Saunders

      Chris Saunders - 2014-11-14

      I see, thanks for the explanation!

       
    • w-peuker

      w-peuker - 2015-01-05

      Wouldn't it be better to rephrase the message then? Today, after upgrading to Cppcheck 1.68, I also see lots if this messages and they are very confusing.

       
  • Daniel Marjamäki

    Yes it sounds like we need to rephraze it. Any suggestions?

    Maybe:

    Configuration X generates the same preprocessor output as configuration Y. The results would be the same for these configurations. Therefore Cppcheck will skip configuration Y.

     
  • Absinthe Sautereau

    How about a way to turn that particular message off?

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks