kdevelop: use LLVM 10 #89100
kdevelop: use LLVM 10 #89100
Conversation
This fixes a bug: https://bugs.kde.org/show_bug.cgi?id=403484 The upstream also prefers LLVM 10: https://cgit.kde.org/kdevelop.git/tree/appimage/Dockerfile?h=5.5#n8
|
How extensively have you tested this? |
|
I use KDevelop in my day job and it works better with this change than without it. Getting KDevelop to correctly highlight the C++ code at my workplace has always been a struggle, perhaps especially since I switched to NixOS, and it's still not perfect right now, so I can't say for completely certain whether the effects of the LLVM upgrade are 100% positive. In that respect I can only point again to the fact that there is an open bug report whose resolution is "don't use LLVM 7", and that upstream themselves use LLVM 10 in their AppImage, which I assume would mean that they have tested it extensively enough. They also seem to have skipped over LLVM 7 entirely, suggesting it might be a uniquely bad version to use: https://cgit.kde.org/kdevelop.git/commit/appimage/Dockerfile?h=5.5&id=1a68e1e97bdbaf81c714dd11a3da9c06d4d84b4a |
|
Sounds good. I tried it out and I don't notice any major regressions. Thanks! |
Motivation for this change
This fixes a bug: https://bugs.kde.org/show_bug.cgi?id=403484
The upstream also prefers LLVM 10: https://cgit.kde.org/kdevelop.git/tree/appimage/Dockerfile?h=5.5#n8
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)I am a user of KDevelop and the bug indeed went away after making this change. I tested on 20.03 which is what I use.