1. 02 Feb, 2018 2 commits
  2. 19 Jan, 2018 1 commit
  3. 18 Jan, 2018 6 commits
    • Christoph Roick's avatar
      Fix SVN history fetching and clean up plugin · 9fd4f6c2
      Christoph Roick authored
      Summary:
      - fetching the history of an svn project only worked sometimes
      - trying to show a diff between versions lead to a crash
      - displaying a diff from the annotation border lead to a crash
      
      - remove UI files which are not used
      - remove unused svncatjob and svncheckoutmetadatawidget
      
      Test Plan:
      - display history/log from vcs context menu entry
      - display diff from history list
      - display diff from annotation border
      - fetch svn project using the assistant
      - commit changes of an svn project
      
      Reviewers: #kdevelop, mwolff
      
      Reviewed By: #kdevelop, mwolff
      
      Subscribers: mwolff, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9956
      9fd4f6c2
    • Kevin Funk's avatar
      debuggercommon: Remove number of lines printed · 57e452e5
      Kevin Funk authored
      ... without losing any information though.
      
      Also, instead of:
         Debugger state changed to: QFlags(0x2|0x100) ""
      
      We now get something like (for Qt >= v5.8.0):
        Debugger state changed to: QFlags<KDevMI::DBGStateFlag>(s_appNotStarted|s_dbgBusy) "" - changes: QFlags<KDevMI::DBGStateFlag>(s_none)
      57e452e5
    • Kevin Funk's avatar
      Attempt to work-around GCC 4.7 bug · 7f437abd
      Kevin Funk authored
      Problem:
        ctestsuite.cpp:104:85: error: lambda-expression in unevaluated context
      7f437abd
    • Milian Wolff's avatar
      Link against KF5::Purpose if it's available · 39c110e3
      Milian Wolff authored
      Summary: The lib is not experimental anymore.
      
      Reviewers: #kdevelop, apol
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9921
      
      (cherry picked from commit 831cf5f9)
      39c110e3
    • Miha Čančula's avatar
      Fix ctestsuites unit test · 51233ccd
      Miha Čančula authored
      Use enable_testing() to always create a CTestTestfile, and prune
      the test project after each test run to remove any stale files.
      
      (cherry picked from commit 8f265cca)
      51233ccd
    • Miha Čančula's avatar
      Fix ctestsuites unit test · 8f265cca
      Miha Čančula authored
      Use enable_testing() to always create a CTestTestfile, and prune
      the test project after each test run to remove any stale files.
      8f265cca
  4. 17 Jan, 2018 3 commits
  5. 16 Jan, 2018 15 commits
  6. 15 Jan, 2018 3 commits
  7. 13 Jan, 2018 1 commit
  8. 10 Jan, 2018 7 commits
    • Milian Wolff's avatar
      Merge branch '5.2' · da4268d3
      Milian Wolff authored
      da4268d3
    • Milian Wolff's avatar
      Performance: Reuse the global icon loader · 94ed49ac
      Milian Wolff authored
      Summary:
      I just found a noticeable GUI hang when showing a problem widget
      for a missing include path. There, the profiler pointed me at
      KIconLoader which was reconstructed whenever we query for the icon
      representing the severity of a problem.
      
      By reusing the global icon loader, we can get the information from
      the cache which is significantly faster.
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9783
      94ed49ac
    • Milian Wolff's avatar
      Cache ProblemPointers per translation unit · f2a6941e
      Milian Wolff authored
      Summary:
      For visibility purposes, all 'inclue file not found' errors are
      associated with all files in a TU, since these usually completely
      break the interpretation of a file. But in some situations, this
      triggers a severe performance degradation:
      
      When the TU has a deep include stack depth and a file is not found
      somewhere at the bottom of the stack, then it will have one child
      diagnostic for every "included from ..." file higher up in the stack.
      Now if we would repeatedly build and intern the KDevelop::Problem
      representation for these diagnostics, for every file in the TU, we
      sometimes ended up spending *minutes* to create all the problems
      in ParseSession::problemsForFile!
      
      To workaround this situation, cache the ProblemPointer in the
      ParseSessionData for a given translation unit. This way, we will
      only convert a given diagnostic and its child diagnostics once per TU
      instead of once per file contained in a TU.
      
      In my case this brings down the time spent in problemsForFile for a
      single TU from ~7min (sic!) down to ~12s. While the latter is still
      a lot, this is already much more bearable.
      
      BUG: 386720
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9772
      f2a6941e
    • Laurent Montel's avatar
      Remove unused file · 3881efbd
      Laurent Montel authored
      (cherry picked from commit d212fa1d)
      3881efbd
    • Laurent Montel's avatar
      Remove unused file · 64c12511
      Laurent Montel authored
      (cherry picked from commit c2031c5d)
      64c12511
    • Friedrich W. H. Kossebau's avatar
      Merge branch '5.2' · b54844ed
      Friedrich W. H. Kossebau authored
      b54844ed
    • Friedrich W. H. Kossebau's avatar
      Only set CMAKE_AUTOMOC_MACRO_NAMES with KF5 < 5.42 · 4a9455fd
      Friedrich W. H. Kossebau authored
      Reviewers: #kdevelop, flherne, kfunk
      
      Reviewed By: #kdevelop, kfunk
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9778
      4a9455fd
  9. 09 Jan, 2018 2 commits