We export include directories for the staging area and staged packages (from `stage-packages`) to allow building this. What we do is for CPPFLAGS, CFLAGS and CXXFLAGS is to add -I directives for the canonical include directories which are on non standard paths.
It seems the SConstruct file for gpsd treats CPPFLAGS differently:
- SConstruct:261 for CFLAGS
- SConstruct:265 for CPPFLAGS
Where the former does a proper split while the latter does a plain join. Given that CPPFLAGS is really the proper way to declare includes (and we use the others for some compatibility with a plethora of build systems) I feel reluctant to just remove CPPFLAGS here.
That said, to unblock you quickly you can change those `stage-packages` to `build-packages`
We export include directories for the staging area and staged packages (from `stage-packages`) to allow building this. What we do is for CPPFLAGS, CFLAGS and CXXFLAGS is to add -I directives for the canonical include directories which are on non standard paths.
It seems the SConstruct file for gpsd treats CPPFLAGS differently:
- SConstruct:261 for CFLAGS
- SConstruct:265 for CPPFLAGS
Where the former does a proper split while the latter does a plain join. Given that CPPFLAGS is really the proper way to declare includes (and we use the others for some compatibility with a plethora of build systems) I feel reluctant to just remove CPPFLAGS here.
That said, to unblock you quickly you can change those `stage-packages` to `build-packages`
Does my assessment sound fair?