Quantcast
Channel: KDevelop - Integrated Development Environment
Viewing all articles
Browse latest Browse all 68

KDevelop 5.0.2 released for Windows and Linux

$
0
0
KDevelop 5.0.2 released for Windows and Linux

Four weeks after the release of KDevelop 5.0.1, we are happy to announce the availability of KDevelop 5.0.2, a second stabilization release in the 5.0 series. We highly recommend to update to version 5.0.2 if you are currently using version 5.0.1 or 5.0.0.

Along with the source code, we release an updated 64-bit AppImage for Linux as well as updated installers for Microsoft Windows. We've got the pleasure to announce a 32-bit version of KDevelop for Windows now, too!

You can find all the downloads on our download page.

KDevelop with two editors open in a split view

Notable issues fixed in 5.0.2 are:

  • Fix a locking issue in the background parser, causing frequent crashes on Windows (3c395340d)
  • Fix broken search in the documentation view (0602281c)
  • Fix various issues with the breakpoints view (cba54572)
  • Fix a possible crash when activating a clang FixIt (BR: 369176)
  • Fix a crash when performing various actions with the Make plugin disabled (BR: 369326)
  • Fix text files being parsed as CMake under some circumstances, leading to bad performance and crashes
  • Use correct font in documentation view (BR: 285162)
  • Fix a crash when clicking "Rename declaration" without an editor being open (22bdccb1)
  • Fix "Download more ..." feature not working on some systems (4c4500bf)
  • Fix "Select next/previous toolview" behaving incorrectly in some cases (24d3e3bb)
  • Fix "Hide/Restore docks" behaving incorrectly in some cases (daeed5f1)
  • Fix "Install as root" action not working (30a66c3f)
  • Fix CMake build plugin sometimes rebuilding everything when it should not (17b6499e)
  • Various UI improvements.

Fixes in the Windows installers:

  • Update Sonnet in the Windows installer which led to crashes when turning on Automatic Spell Checking [BR: 370470]
  • Fix heap corruption after start / immediately after opening folder [BR: 370495]

The source code can be downloaded from http://download.kde.org/stable/kdevelop/5.0.2/src/.

You can find the binaries for Windows and Linuxon our download page.

The source code archives and their sha-256 checksums are

24ec89b4edc854808ce11a8e8b0aeb853f11926b26029bc46c80f901da00aec7  kdev-php-5.0.2.tar.xz
5d160951933e2f6742a443e19d24e0c93a82567244500e4bb6a3124e5e4e11ff  kdev-python-5.0.2.tar.xz
9b017901167723230dee8b565cdc7b0e61762415ffcc0a32708f04f7ab668666  kdevelop-5.0.2.tar.xz
a7f311198bb72f5fee064d99055e8df39ecf4e9066fe5c0ff901ee8c24d960ec  kdevplatform-5.0.2.tar.xz

For verifying integrity and authenticity of the files, the preferred method is to use the provided GPG signature files (.sig).
All downloads are signed with the GPG key of Sven Brauch, fingerprint 329F D02C 5AA4 8FCC 77A4  BBF0 AC44 AC6D B297 79E6.

sbrauchMon, 10/17/2016 - 13:15
Category

Comments

Good show! I've updated the FreeBSD packaging of KDevelop 5.0 to this latest release (although it'll still be a while before that hits the official package servers). Thanks for creating KDevelop.

Great, hope it can solve my problem of "Unable to resolve symbol of KDE_PLUGIN_VERSION" of 5.0.1.

Btw, with 5.0.1 I can only have templates for KDE4, but no templates of KDE5, I think this may caused by the issue I mentioned above, will try the new one.

I'm a bit confused about how the Windows version of 5.0 works. My understanding was that your using clang as the backend for all syntax highlighting and understanding of the code in version 5.0 of KDevelop. How does this work when on the Windows setup docs you say you can only use GCC (via MinGW) or Visual Studio? Does this mean that you are using Visual Studio for the Syntax highlighting and error messages, etc? Does that mean that your using the old parser that wasn't great? If this is the case is there any real reason to use KDevelop over other IDEs on Windows? Really hoping I am just missing something as KDevelop 5 on Linux is amazing and I would love to replace Visual Studio with it there as well.

Permalink

In reply to by James (not verified)

Hey. For 5.0 we use the Clang backend on all platforms, that is Linux, OS X and Windows. All our C/C++ language support from 5.0 onwards is based on libclang (cf. http://clang.llvm.org/doxygen/group__CINDEX.html).

We don't use VS nor do we use our "old parser". You can also use KDevelop with any compiler on Windows, be it MinGW, Visual Studio or even Clang on Windows; we don't actually care.

What about just downloading the Windows version and giving it a spin? Would love to hear your feedback!

Just tried out the linux AppImage on our Debian 7 (KDE 4.8) workplace platform. I wasn't able to run the image directly (missing fuse), but after renaming the image with an .iso extension, extracting the contents in ark, and launching AppRun, I am happy to see it running well! As we will be on Debian 7 for a little while longer, it's great to see that we will be able to run the latest KDevelop on an "old" system. Kudos!

One item that wasn't working out of the box is spellcheck: Settings > Configure KDevelop > Editor > Editing > Spellcheck would display "No backend found for spell checking". After grabbing the debian sonnet-plugins package and extracting aspell.so, hspell.so, and hunspell.so to usr/lib/qt5/plugins/kf5/sonnet/ (in the tree extracted from the AppImage), spellchecking is back in business. Perhaps you can include these libs in future AppImage distributions.

On kdevelop 4.7.2 we rely heavily on the kdevperforce and kdevcppcheck plugins. Any chance the kdevelop 5 libs for these plugins can be distributed as well, or made available in a separate package? Unfortunately I have no straightforward means of building them...

Permalink

In reply to by Martin (not verified)

One item that wasn't working out of the box is spellcheck

For this I've created https://phabricator.kde.org/T4100 -- you'll probably get that in another AppImage update.

On kdevelop 4.7.2 we rely heavily on the kdevperforce and kdevcppcheck plugins

kdev-perforce will be part of 5.1. You'll get that in the 5.1 AppImage.

kdev-cppcheck unfortunately isn't released yet. We'd like to only ship released & tested modules in the AppImage. Let's see how far we get with cppcheck, maybe we can integrate it into KDevelop proper -- contributions welcome!


Viewing all articles
Browse latest Browse all 68

Trending Articles