extensions/gnome: Add sdk include directories to C_INCLUDE_PATH#5514
extensions/gnome: Add sdk include directories to C_INCLUDE_PATH#55143v1n0 wants to merge 1 commit intocanonical:mainfrom
Conversation
01a2c43 to
b535fb0
Compare
The sdk provides a base /usr/include path that should be checked when an including from the default paths. Without this, when a file is including something such as #include <xkbcommon/xkbcommon.h> that is provided by /snap/gnome-46-2404-sdk/current/usr/include, the compiler won't look for such path at all. However do this only for core24, because in core22 the clang version does not handle it properly, breaking flutter builds
mr-cal
left a comment
There was a problem hiding this comment.
Is there any risk of this breaking existing core24 snaps using the gnome extension?
The snaps no, builds it may... But well at rebuild time adjustments can be done. However we're using it already in the sdk |
This seems risky then. Our user contract is that an unchanged file should continue to build (as much as is in our control). There's an exception for stuff that's marked as experimental, but this extension is already marked as stable for core24. The final call right now is @bepri's, but I think I'd rather add this for core26+ |
|
I think I agree with @lengau - I don't think it matters if it's an easy fix, needing a fix to a project file without a major version bump to Snapcraft is bad behavior. Another exception I've seen is for bugfixes, but this doesn't seem like a bug to me either. I say this should be delayed until Snapcraft 9/core26. |
The sdk provides a base /usr/include path that should be checked when an including from the default paths.
Without this, when a file is including something such as
that is provided by /snap/gnome-46-2404-sdk/current/usr/include, the compiler won't look for such path at all.
There's no need to fallback to default
/usr/includebecause such path is always included anyways by gcc (at least when that's compiled with such prefix).make lint?make test?