1. 16 Jan, 2022 2 commits
  2. 15 Jan, 2022 5 commits
  3. 13 Jan, 2022 1 commit
  4. 08 Jan, 2022 2 commits
    • Alexander Lohnau's avatar
      kcoreaddons_add_plugin: Throw error when we have unparsed args · 953e8140
      Alexander Lohnau authored
      In case one forgets to add the `SOURCES` option before passing in the files,
      we would simply not add them to the library and don't emit any kind of warning.
      
      In case of static plugins we would get a build error, but for dynamic plugins we would
      only get a semi-useful error from QPluginLoader that no plugin/metadata could be found.
      
      Considering that the unexpected argument can be a long list of arguments, I don't think
      it is worth printing it out. Consumers should check out the docs for the usage information.
      953e8140
    • Script Kiddy's avatar
      GIT_SILENT Upgrade KF version to 5.91.0. · 3363506d
      Script Kiddy authored
      3363506d
  5. 07 Jan, 2022 2 commits
  6. 06 Jan, 2022 2 commits
  7. 03 Jan, 2022 5 commits
  8. 02 Jan, 2022 3 commits
  9. 01 Jan, 2022 1 commit
  10. 29 Dec, 2021 4 commits
  11. 28 Dec, 2021 2 commits
    • Alex Richardson's avatar
      FindProcstat: Fix CMake warning and use an imported target · b6f5a336
      Alex Richardson authored
      Previously we were getting the following warning:
      ```
      The package name passed to `find_package_handle_standard_args` (PROCSTAT)
      does not match the name of the calling package (Procstat).  This can lead
      to problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
      ```
      b6f5a336
    • Ahmad Samir's avatar
      Don't put the plugins in a "/plugins" sub-dir in the builddir · 375e19cf
      Ahmad Samir authored and Alexander Lohnau's avatar Alexander Lohnau committed
      This restores the old behaviour of putting the plugins .so files in
      builddir/bin/<plugin_name_space>, where plugin_name_space is e.g.
      "kf5/kio/".
      
      This has the advantage of working as QCoreApplication::libraryPaths()
      will pick it up automatically, so if you run a unittest on the CLI,
      (without ctest) in gdb ...etc, it'll just work.
      375e19cf
  12. 27 Dec, 2021 1 commit
    • Janet Blackquill's avatar
      KPluginFactory: report errors from QPluginLoader · ff6997eb
      Janet Blackquill authored
      This makes error messages more helpful for debugging.
      
      Example:
      
      kf.coreaddons: "Could not load plugin from /home/jpontaoski/kde/usr/lib64/plugins/kisspages/libpage_user.so: Die Bibliothek /home/jpontaoski/kde/usr/lib64/plugins/kisspages/libpage_user.so kann nicht geladen werden: (/home/jpontaoski/kde/usr/lib64/plugins/kisspages/libpage_user.so: undefined symbol: _ZN4Page16staticMetaObjectE)
      
      (after)
      
      vs
      
      kf.coreaddons: "Could not load plugin from /home/jpontaoski/kde/usr/lib64/plugins/kisspages/libpage_user.so"
      
      (before)
      ff6997eb
  13. 25 Dec, 2021 1 commit
  14. 23 Dec, 2021 1 commit
  15. 18 Dec, 2021 2 commits
  16. 15 Dec, 2021 1 commit
  17. 13 Dec, 2021 1 commit
  18. 11 Dec, 2021 2 commits
  19. 10 Dec, 2021 2 commits