1. 10 Jun, 2016 1 commit
  2. 01 Jun, 2016 2 commits
  3. 30 Mar, 2016 1 commit
  4. 20 Jan, 2016 2 commits
  5. 26 Jun, 2015 1 commit
  6. 09 Feb, 2015 1 commit
    • Christian Kandeler's avatar
      Add unit tests. · 2946364c
      Christian Kandeler authored
      These test the complete workflow as the user experiences it when
      clicking "Start".
      Intended usage:
          (1) Run sdktool to set up a kit with the toolchain you want
              to test against (using a temporary directory).
              The tests assume exactly one Kit to be present.
          (2) Start Creator with a matching settings path and
              "-load ClangStaticAnalyzer -test ClangStaticAnalyzer".
          (3) Repeat until all toolchains have been tested.
      The initial implementation tests one trivial source file
      with both qbs and qmake.
      Change-Id: I810f23e2990a789a4dd9f1dd16335fbcf5c5f39f
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
  7. 15 Jan, 2015 1 commit
  8. 16 Oct, 2014 1 commit
    • Nikolai Kosjar's avatar
      Import Clang Static Analyzer plugin · b9f9eb7a
      Nikolai Kosjar authored
      This plugin adds "Clang Static Analyzer" to the Analyze mode, which
      processes all implementation/source project files of the current
      project. For this, it will call the clang executable for each file.
      The found diagnostics will be displayed in a view similar to the one
      used in "Valgrind Memory Analyzer".
      The user can specify the clang executable to use and the number of
      concurrent processes to launch in Menu: Tools > Options > Analyzer >
      Clang Static Analyzer.
      Main TODOs:
       * Fiddle around the appropriate command line options, currently only
         defines and include paths are passed on.
       * Tests on Windows / OS X.
       * Remove dependency to clangcodemodel by moving the functions that
         create command line arguments to CppTools. Mostly they are not even
         specific to clang (but would also work with gcc).
       * Maybe limit to a range of tested clang versions.
       * How to deal with directory containing all the log files after the
         user starts a new run or Creator is shut down? (delete it? leave it
         there? make it configurable?).
       * Find out how to properly integrate the tests.
      Imaginable future additions:
       * Adding a button to load result/log files from a directory, e.g. if
         the user used the 'scan-build' approach.
       * Adding a button with a filter menu in order to display only
         diagnostics from certain categories, similar to "Valgrind Memory
      Change-Id: I6aeb5dfdbdfa239a06c03dd8759a983df71b77ea
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>