/usr/local/include in _KDE4_PLATFORM_INCLUDES on FreeBSD?

Alexander Neundorf neundorf at kde.org
Tue May 18 23:05:37 CEST 2010


On Saturday 15 May 2010, Raphael Kubo da Costa wrote:
> On Monday 10 May 2010 19:26:25 Raphael Kubo da Costa wrote:
> > On Monday 10 May 2010 19:13:49 Alexander Neundorf wrote:
> > > On Tuesday 11 May 2010, Raphael Kubo da Costa wrote:
> > > > On Monday 10 May 2010 18:54:31 Alexander Neundorf wrote:
> > > > > On Monday 10 May 2010, Raphael Kubo da Costa wrote:
> > > > > > Hey there,
> > > > > >
> > > > > > I was trying to update kdelibs today on FreeBSD and noticed
> > > > > > nepomuk kept failing to compile because some methods were not
> > > > > > found in Soprano.
> > > > > >
> > > > > > It turns out kdelibs/nepomuk/query/CMakeLists.txt's
> > > > > > include_directories() call put KDE4_KDECORE_INCLUDES before
> > > > > > SOPRANO_INCLUDE_DIR, so my system-wide Soprano headers (in
> > > > > > /usr/local/include) were being used instead of my trunk Soprano
> > > > > > headers in $HOME/kde4/include.
> > > > > >
> > > > > > Apparently, /usr/local/include was coming from
> > > > > > _KDE4_PLATFORM_INCLUDE_DIRS.
> > > > >
> > > > > This must be X11_INCLUDE_DIR. Can you confirm this ?
> > > >
> > > > According to what I saw on FindKDE4Internal.cmake yesterday, yes. And
> > > > yes, X11 is inside /usr/local.
> > >
> > > Hmm, we could remove X11_INCLUDE_DIR. One could argue whether this
> > > would be a bugfix or a potentially source incompatible change.
> > > But even then, couldn't this also happen with any other include dirs
> > > used in the "right" order ?
> >
> > Hmm, you mean if some other dependency was found in /usr/local and it
> > ended up being included via include_directories() before
> > $MYLOCALKDEPREFIX? Probably...
> >
> > I'm not sure if there's a proper "fix" for this. Why isn't /usr included
> > by CMake?
>
> Ping? :)

Hmm, I think there may be no better solution than to manually take care of a 
good order for the include directories...
I mean, removing X11_INCLUDE_DIR there would fix this one issue, but this can 
happen for other packages too...

Alex


More information about the Kde-buildsystem mailing list