Bug 499768

Summary:	Latest nightly appimage (feb 10 2024) does not parse c++
Product:	[Applications] kdevelop	Reporter:	Ian H <master.haber>
Component:	Language Support: CPP (Clang-based)	Assignee:	kdevelop-bugs-null
Status:	REPORTED ---
Severity:	normal	CC:	igorkuo
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ian H 2025-02-10 16:59:50 UTC

SUMMARY
When running the latest nightly appimage, kdevelop does not parse files with clang and gives this error: 

kdevplatform.shell: Could not load plugin "kdevclangsupport" , it reported the error: "The clang builtin include path \"/builds/kdevelop/kdevelop/linux-64-gcc/lib/clang/18/include\" is invalid (missing cpuid.h header).\nTry setting the KDEV_CLANG_BUILTIN_DIR environment variable manually to fix this.\nSee also: https://bugs.kde.org/show_bug.cgi?id=393779" Disabling the plugin now.


STEPS TO REPRODUCE
1. download nightly from https://cdn.kde.org/ci-builds/kdevelop/kdevelop/master/linux/
2. run nightly in console

OBSERVED RESULT
parsing does not work and will give error in console



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ubuntu 2022

Comment 1 Igor Kushnir 2025-02-10 17:50:02 UTC

Looks like we don't bundle Clang headers into the AppImage. I don't fancy studying AppImage format/specification to fix this. A merge request is welcome.

Comment 2 Igor Kushnir 2025-02-10 18:04:39 UTC

Actually fixing this may require some knowledge of KDE Craft. Perhaps the Clang built-in include path in the file https://invent.kde.org/packaging/craft-blueprints-kde/-/blob/acd78b0681dec3f861bb5c26a781cde066a951e5/extragear/kdevelop/kdevelop/whitelist.txt needs to be adjusted.

Comment 3 Ian H 2025-02-12 17:34:45 UTC

the latest flatpak also does something similar to this, but the error it gives is this:

kf.coreaddons: "Could not load plugin from /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: Cannot load library /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: libclang.so.19.1: cannot open shared object file: No such file or directory"
kdevplatform.shell: Can't load plugin "kdevclangsupport" because a factory to load the plugin could not be obtained: "Could not load plugin from /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: Cannot load library /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: libclang.so.19.1: cannot open shared object file: No such file or directory"

Would you prefer i separate this to a different bug or leave it here?

Comment 4 Igor Kushnir 2025-02-12 17:50:04 UTC

(In reply to Ian H from comment #3)
> kf.coreaddons: "Could not load plugin from
> /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: Cannot load library
> /app/lib/plugins/kdevplatform/61/kdevclangsupport.so: libclang.so.19.1:
> cannot open shared object file: No such file or directory"
So the Flatpak does not even bundle libclang? I don't know who maintains KDevelop Flatpak, but looks like no one tests it.

> Would you prefer i separate this to a different bug or leave it here?
A separate bug please. I think the issues are quite different and each bug can be addressed separately.

Comment 5 Ian H 2025-02-12 19:43:05 UTC

(In reply to Igor Kushnir from comment #4)
> So the Flatpak does not even bundle libclang? I don't know who maintains
> KDevelop Flatpak, but looks like no one tests it.

lol that's kindof how i feel about every packaged version of kdevelop. i've yet to see a single one work since the appimages stopped getting put on the kdevelop site download page. This is why i'm still using version 5.5. 

i can never even get it to build from source, lol. the fact that your CI is actually building is astonishing to me. (this one is never a kdevelop issue, but rather kdesrc-build always being buggy for me)