1. 25 Feb, 2019 1 commit
  2. 20 Jan, 2019 1 commit
  3. 20 Nov, 2018 1 commit
  4. 19 Nov, 2018 1 commit
  5. 26 Oct, 2018 1 commit
  6. 25 Oct, 2018 1 commit
  7. 24 Oct, 2018 2 commits
  8. 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
  9. 29 Aug, 2018 1 commit
  10. 26 Aug, 2018 1 commit
  11. 24 Aug, 2018 1 commit
  12. 13 Mar, 2018 2 commits
  13. 06 Jan, 2018 2 commits
  14. 01 Jan, 2018 2 commits
  15. 04 Dec, 2017 1 commit
  16. 22 Nov, 2017 3 commits
  17. 21 Nov, 2017 1 commit
  18. 17 Nov, 2017 2 commits
  19. 24 Oct, 2017 1 commit
  20. 28 Sep, 2017 1 commit
  21. 13 Sep, 2017 1 commit
  22. 20 Jun, 2017 1 commit
  23. 23 May, 2017 1 commit
  24. 22 May, 2017 1 commit
    • Aleix Pol Gonzalez's avatar
      Introduction of runtimes · 1e0bd1f4
      Aleix Pol Gonzalez authored
      Summary:
      When we develop our software, we usually don't develop the application just
      for us. In the linux world we have a big problem with distributing our
      software beyond software tarballs and this abstraction aims at integrating
      the solutions created for deploying software so that it can be integrated
      in our workflow when developing.
      
      As you can see in the proposed IRuntime class, there's 2 main things
      abstracted:
      * the file system, by converting file paths into the runtimes' back and
      forth. (e.g. include directories)
      * processes, by running the processes we execute to interact and
      introspect the system (i.e. cmake or gdb)
      
      For a proof of what we're discussing, I implemented two plugins: flatpak
      and docker.
      - docker: is more of a proof of concept nowadays, in general it just works
      in terms of running processes but there we don't (yet?) have integration
      with the file system.
      - flatpak: allows us a full-featured environment for creating and deploying
      desktop applications, which offers many simplifications over how we've been
      working so far.
      
      Here's a couple of videos showing the kind of things we can do and a
      proposal for a workflow.
      
      Docker: https://youtu.be/7a4qbQ1rrYc
      Flatpak: https://youtu.be/Gh9nT7tFI6g
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D5584
      1e0bd1f4
  25. 12 May, 2017 1 commit
    • Friedrich W. H. Kossebau's avatar
      Default to disabled debug log on Q_LOGGING_CATEGORY calls · ddf0a6fc
      Friedrich W. H. Kossebau authored
      Summary:
      This removes the need to call QLoggingCategory::setFilterRules()
      in the program code to default to disabled debug type log
      without any other settings.
      The latter has disadvantages, as it shadows any settings done
      in qtlogging.ini config files by the user
      (e.g. via kdebugsettings), thus enabling runtime control only
      via QT_LOGGING_CONF/QT_LOGGING_RULES, which is not that
      comfortable with lots of categories.
      
      Also use ECMQtDeclareLoggingCategory for less manual code
      
      While there can be some inconsistency with the default disabled
      log categories by ECMQtDeclareLoggingCategory, which
      switched to QtInfoMsg for ECM 5.26 (when KF5 5.26 has Qt 5.5
      as min dep, which is the Qt version QtInfoMsg was added),
      current KDevPlatform code has Qt 5.4 as minimum version and
      thus also does not use qCInfo, so KDevPlatform behaviour should
      be the same across used Qt versions.
      
      Reviewers: #kdevelop, kfunk
      
      Reviewed By: #kdevelop, kfunk
      
      Subscribers: apol, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D5666
      ddf0a6fc
  26. 09 Apr, 2017 2 commits
  27. 03 Apr, 2017 1 commit
  28. 01 Apr, 2017 1 commit
  29. 23 Mar, 2017 1 commit
  30. 18 Mar, 2017 1 commit
  31. 16 Mar, 2017 1 commit
    • Friedrich W. H. Kossebau's avatar
      Remove unused/unneeded includes & forward declarations · ec809d58
      Friedrich W. H. Kossebau authored
      Summary:
      Some people play Sudoku on the train, others play
      Gredelbuil (grep, remove, build), i.e. manually cleaning up
      includes and forward declarations which are not needed
      
      Done by primitive grepping for Q/K* class names and
      * removing any includes whose class does not have instances
        by a quick look in implementations in the same file
      * using forward declarations instead of includes for classes
        whe possible, unless a template class (because the latter
        is quite verbose as forward declarations, the include
        nicer to read)
      * removing any forward declarations which are not used in the
        same file
      (one day a bot/script will steal my game and beat me, o tempores)
      
      WRT effects on dependent code, at least kdevelop will need one or
      two adaptions due to changed include visibility. That is done as
      part of a similar clean-up patch, which will be either directly
      pushed or also passed through review, as you prefer.
      
      Reviewers: #kdevelop, apol
      
      Reviewed By: #kdevelop, apol
      
      Subscribers: apol, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D5071
      ec809d58
  32. 07 Mar, 2017 1 commit