kdesupport/soprano/includes

Sebastian Trüg sebastian at trueg.de
Fri Oct 5 18:16:21 BST 2007


On Friday 05 October 2007 18:46:37 Christian Ehrlicher wrote:
> Sebastian Trüg schrieb:
> > On Friday 05 October 2007 18:35:16 Rafael Fernández López wrote:
> >> Hi all,
> >>
> >> This is crazy ! the thread splitted in different lists...
> >>
> >> El Friday 05 October 2007 17:43:59 Christian Ehrlicher escribió:
> >>> Jarosław Staniek schrieb:
> >>>> Rafael Fernández López said the following, On 2007-10-05 15:47:
> >>>>> Hi,
> >>>>>
> >>>>> Right. At the moment on include folder I have soprano and Soprano
> >>>>> folders installed. This will fail on windows... at least I think
> >>>>> so...
> >>>>>
> >>>>> Any input from windows systems ?
> >>>>
> >>>> How about libsoprano/ ?
> >>
> >> Sebastian ? What do you think ?
> >
> > I think it is a little ugly.
> >
> >>> I still don't understand why you need include/soprano (file) at all -
> >>> either you use a subdir and put *all* your files into your you don't...
> >>
> >> Sebastian ? ^^
> >
> > I don't get it. I use a subdir with all files in it. The problem is that
> > I have two subdirs: one with the standard includes such as "statement.h"
> > and one with the "nice" includes such as "Statement". Once is called
> > "soprano" and the other one "Soprano". That is the problem since Windows
> > apparently still does not take case into account in file management.
> > Maybe one solution would be to add yet another folder layer and add it to
> > the include path in FindSoprano.cmake:
> >        soprano/niceincludes/Soprano
> > or something like that.
> >
> > Or we just plain remove the nice includes. :(
>
> Ok, now I understand - I thought one of them is a file.
> Then I prefer soprano and soprano-devel (or whatever those files are for)

soprano-devel? Which one? The standard includes?




More information about the kde-core-devel mailing list