1. 24 Nov, 2014 1 commit
  2. 20 Nov, 2014 1 commit
  3. 18 Nov, 2014 1 commit
  4. 14 Nov, 2014 1 commit
  5. 07 Nov, 2014 6 commits
  6. 03 Nov, 2014 1 commit
  7. 31 Oct, 2014 4 commits
  8. 29 Oct, 2014 1 commit
  9. 28 Oct, 2014 2 commits
  10. 27 Oct, 2014 2 commits
  11. 24 Oct, 2014 6 commits
  12. 23 Oct, 2014 2 commits
  13. 22 Oct, 2014 3 commits
  14. 16 Oct, 2014 3 commits
    • Eike Ziller's avatar
      Only build it if the clang code model would be built · 1bd59110
      Eike Ziller authored
      
      
      Change-Id: I8e2ecb56f0c6cfdcbdce9b580db84f3c6c5c709e
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      1bd59110
    • Eike Ziller's avatar
      There is no PROVIDER anymore · 65f5c4c7
      Eike Ziller authored
      
      
      Change-Id: Id78aa8deda3907bd586726e0def1aba47ad6da1a
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      65f5c4c7
    • 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
         Analyzer".
      
      Change-Id: I6aeb5dfdbdfa239a06c03dd8759a983df71b77ea
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      b9f9eb7a
  15. 15 Oct, 2014 1 commit