1. 28 Aug, 2019 2 commits
  2. 26 Aug, 2019 2 commits
  3. 22 Aug, 2019 1 commit
  4. 07 Aug, 2019 1 commit
  5. 04 Aug, 2019 1 commit
  6. 25 Jul, 2019 1 commit
  7. 24 Jul, 2019 1 commit
  8. 22 Jul, 2019 2 commits
  9. 21 Jul, 2019 1 commit
  10. 13 Jul, 2019 1 commit
  11. 17 Jun, 2019 1 commit
  12. 16 Jun, 2019 1 commit
  13. 03 Jun, 2019 4 commits
  14. 20 May, 2019 2 commits
  15. 30 Apr, 2019 1 commit
    • Kai Uwe Broulik's avatar
      Add DesktopEntry to notifyrc · e9c489eb
      Kai Uwe Broulik authored
      Summary: This allows the notification KCM to identify KDevelop as an application.
      
      Test Plan:
      {F6801449}
      This can probably go to stable since older Plasma/Frameworks will just ignore that field
      
      Reviewers: #kdevelop, kfunk
      
      Reviewed By: #kdevelop, kfunk
      
      Subscribers: kfunk, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D20920
      e9c489eb
  16. 19 Feb, 2019 1 commit
  17. 10 Feb, 2019 1 commit
    • Milian Wolff's avatar
      kdevelop-msvc.bat finds VS-2017 based on a registry key on Windows. · 7e4294a8
      Milian Wolff authored
      Summary:
      Some months earlier, we discussed [[ https://phabricator.kde.org/D15976 | here ]] about `kdevelop-msvc.bat` finding dynamically a VS2017 installation based on registry entries.
      
      Although it works on my Dell laptop (Windows 7 Ultimate x64), I haven't tested it anywhere else as I don't have access to another windows machine. So... any takers?
      
      Test Plan: In case some user has installed VS in a non-standard location (i.e. not in `C:\Program Files`), the script will be able to find the VS tools by not making the assumption that they are installed on `C:\`.
      
      Reviewers: #kdevelop, kfunk, brauch, mwolff
      
      Reviewed By: #kdevelop, mwolff
      
      Subscribers: mwolff, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D17908
      7e4294a8
  18. 04 Feb, 2019 1 commit
    • Friedrich W. H. Kossebau's avatar
      Set StartupWMClass in main kdevelop desktop file · 792cb4f9
      Friedrich W. H. Kossebau authored
      Used by non-Plasma unixoid X-based shells to map windows to desktop files
      e.g. in launcher UIs, which do not know about _KDE_NET_WM_DESKTOP_FILE and
      instead expect the WM_CLASS to match the basename of the desktop file
      by default. StartupWMClass overwrites that default.
      792cb4f9
  19. 20 Jan, 2019 2 commits
  20. 06 Jan, 2019 2 commits
  21. 03 Jan, 2019 1 commit
  22. 29 Dec, 2018 1 commit
  23. 17 Dec, 2018 1 commit
  24. 20 Nov, 2018 2 commits
  25. 28 Oct, 2018 1 commit
  26. 25 Oct, 2018 1 commit
  27. 23 Oct, 2018 1 commit
    • Friedrich W. H. Kossebau's avatar
      Generate all kdebugsettings .categories files automatically · 774429d0
      Friedrich W. H. Kossebau authored
      Summary:
      Adds two wrapping variants of the macros
      declare_qt_logging_category() & install_qt_logging_categories()
      which have an argument TYPE to control specific behaviour that
      otherwise is generalized in the wrapping macros to not have to repeat
      any things with every macro call and to ensure consistency, e.g. in
      the used description texts.
      
      The wrapper macros also handle linking things by the matching EXPORT ids,
      so the caller does not have to care for this.
      
      No perfect solution yet, but at least a first working approach to automatic
      generation of the kdebugsettings files.
      
      Test Plan:
      Generated categories files contain same ids with same descriptions as
      before.
      
      Reviewers: #kdevelop, kfunk
      
      Reviewed By: #kdevelop, kfunk
      
      Subscribers: kfunk, apol, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D16032
      774429d0
  28. 12 Oct, 2018 1 commit
    • Kevin Funk's avatar
      windows: Detect VS2017 compiler and tools · ea3d601f
      Kevin Funk authored
      Summary:
      Visual Studio 2017 defines the VS150COMNTOOLS env variable which
      kdevelop-msvc.bat ignored till now. By default VS does not set the
      VS150COMNTOOLS as system-wide variable so we have to do be a bit more
      clever to detect the VS2017 install.
      
      Also allow to start using VS2017 compiler, using either 32 bit or 64 bit
      compilers by prompting the user.
      
      Reviewers: Petross404, brauch
      
      Reviewed By: brauch
      
      Subscribers: brauch, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D16123
      ea3d601f
  29. 11 Oct, 2018 2 commits