Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

  1. 12 Aug, 2016 1 commit
  2. 18 Jul, 2016 1 commit
  3. 14 Jul, 2016 1 commit
  4. 28 Jun, 2016 1 commit
  5. 24 Jun, 2016 1 commit
  6. 23 Jun, 2016 1 commit
  7. 02 Jun, 2016 1 commit
    • Friedrich W. H. Kossebau's avatar
      Use Vc 1.1 as minimum · cf76bbcd
      Friedrich W. H. Kossebau authored
      As Krita seems to be still the main user of Vc and thus driving the
      adaption, go straight to the latest known working version, to skip
      any problems with slightly older versions, as the latest version
      "should" be the best after all.
      
      Reviewed By: rempt
      
      Differential Revision: https://phabricator.kde.org/D1750
      cf76bbcd
  8. 30 May, 2016 1 commit
  9. 29 May, 2016 1 commit
  10. 22 May, 2016 1 commit
  11. 16 May, 2016 3 commits
  12. 12 May, 2016 1 commit
  13. 02 May, 2016 1 commit
    • Boudewijn Rempt's avatar
      BUG:361973 Remove all our custom mime types · d9c68ec2
      Boudewijn Rempt authored
      This should fix bug 361973 even for people who build Krita on
      their own. It must be a bug somewhere in Qt, and a recent
      regression, too. Just stopping to use QMimeDataBase doesn't
      fix it, since it's some Qt-internal usage that breaks everything
      in QFileDialog if there is a mime directory in the XDG_DATA_DIRS.
      d9c68ec2
  14. 27 Apr, 2016 2 commits
  15. 25 Apr, 2016 1 commit
  16. 22 Apr, 2016 8 commits
  17. 14 Apr, 2016 2 commits
  18. 11 Apr, 2016 4 commits
  19. 09 Apr, 2016 7 commits
  20. 07 Apr, 2016 1 commit
    • Thorsten Zachmann's avatar
      Update krita to compile against Vc >= 1.0.0 · b68c1c76
      Thorsten Zachmann authored
      This updates krita to work with Vc version 1.0.0 and above. Some changes to the
      build system were needed as the compile options are now set differently. The
      compile flags are set on the lib which uses the functionality. This is needed in
      a non packager build only. Compile the KisCompositionBenchmark against the
      current available Vc optimization.
      
      Thanks to Vir for all his help.
      
      Tested packager and non packager build. Run the and compared the output of
      ./KisCompositionBenchmark.shell. The speed is nearly the same. For avx a
      different code path is used when avx2 is not available which makes it tick
      slower but correct in all cases according to Vir.
      
      Compiled and tested against vc 1.0.0 and vc 1.2.0.
      b68c1c76