[Sebastian Treug] Problems compiling kdebase-4.3 due to trig

View: New views
3 Messages — Rating Filter:   Alert me  

[Sebastian Treug] Problems compiling kdebase-4.3 due to trig

by abhinavc :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi Sebastian,
I tried what you suggested. And this is what I got:

redland-config --version = 1.0.8
raptor-config --version = 1.4.18
rasqal-config --version = 0.9.16

Attached are 2 files:
1. CMakeCache.txt file in the build folder one needs to create before compiling Soprano
2. CMakeLists.txt file from ../build

I see options like SOPRANO_DISABLE_RAPTOR_PARSER:BOOL=OFF in
the CMakeCache.txt file. So I am thinking that everything that is needed should have been compiled from scratch. Did I miss something when doing 'cmake'?

Thanks
Abhinav. 


2009/11/10 <kde-core-devel-request@...>
Send kde-core-devel mailing list submissions to
       kde-core-devel@...

To subscribe or unsubscribe via the World Wide Web, visit
       https://mail.kde.org/mailman/listinfo/kde-core-devel
or, via email, send a message with subject or body 'help' to
       kde-core-devel-request@...

You can reach the person managing the list at
       kde-core-devel-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kde-core-devel digest..."


Today's Topics:

  1. Re: Review Request: startup faster;       don't wait for kwin or
     kcm's in ksmserver (Lubos Lunak)
  2. Re: chess and barcelona (Marco Martin)
  3. Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to
     trig (Sebastian Trueg)


----------------------------------------------------------------------

Message: 1
Date: Mon, 9 Nov 2009 14:56:33 +0100
From: Lubos Lunak <l.lunak@...>
Subject: Re: Review Request: startup faster;    don't wait for kwin or
       kcm's in ksmserver
To: kde-core-devel@...
Message-ID: <200911091456.33717.l.lunak@...>
Content-Type: text/plain;  charset="utf-8"

On Saturday 07 of November 2009, Sebastian Sauer wrote:
> > On 2009-11-04 10:10:06, Lubos Lunak wrote:
> > > The reason for waiting for the WM to finish setup is not the fallback,
> > > but making sure the WM is ready. There are some aspects related to
> > > window management where applications just read the status during their
> > > startup and don't update later. So waiting for the WM ensures this is
> > > set up properly before other applications may read that (although,
> > > thinking of that, this is currently a bit broken anyway, as KWin lets
> > > ksmserver continue a bit too soon).
> > >
> > > The second case is something similar. The kcminit modules do various
> > > setup and it is a question if it is ok to let normal apps start while
> > > this is still taking place.
>
> Specs are relative. Cold start (not initial) takes up to 9 seconds till the
> plasma desktop is visible / ksplashx closes.

 Hmm. Twice 1/2s is not that insignificant then :-/.

> The thing is that the wm starts very early. Even before plasma which does
> not need the wm at this point. The first "real" applications are rather
> late started/restored. Maybe we should just wait in
> KSMServer::autoStart1Done() till the wm is ready? Would that be enough?

 Plasma is not different from other applications in this regard, in fact, it
may depend more on it - compositing status, number of virtual desktops, etc.
I have no idea what would happen if e.g. Plasma thought there was just 1
virtual desktop because it saw that too soon.

> The kde startup process has lot of potential for optimizations.

 It is intentionally designed that way. The original application launching
code (around KSMServer::tryRestoreNext()) is written to launch apps one by
one. IIRC the reason for that was that computers[*] of those days were bad at
handling the load and putting sleeps here and there actually improved the
overall situation. I doubt anyone has benchmarked this in a reasonably recent
time.

[*] Or maybe we could blame the kernel.

> Time
> expensive things like e.g. kcminit are atm blocking the whole startup. Long
> term we need to have expensive things run in parallel at startup. Anyway,
> if you think that this is not a good idea then it should be maybe done
> another way.

 I don't know if there is another way. The code can be changed to launch
normal apps in parallel if that helps, there would be no problem with that.
But the rest currently has certain ordering (see ksmserver/README) with some
implications. For example startup phase 0 (i.e. Plasma) is done quite early
and waited for completion in order to have the desktop ready, hide the splash
and give the impression that the desktop or more or less ready while normal
apps are still being loaded. Moving things one way can mean the splash is
shown needlessly long when the desktop could be already usable, opposite way
would be showing desktop that is still not usable (as is the case with some
Windows versions and AFAIK it's rather annoying).

 If you would have some time to spend on this, it would be interesting if you
could analyze the KDE startup as a whole and see where the time is spent
(note: cold vs warm disk caches did tripple the number when I tested that the
last time, so pay attention to that). With that thinking about doing some
rearranging should be simpler.

--
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak@... , l.lunak@...
Lihovarska 1060/12   tel: +420 284 084 672
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http://www.suse.cz


------------------------------

Message: 2
Date: Mon, 9 Nov 2009 17:22:02 +0100
From: Marco Martin <notmart@...>
Subject: Re: chess and barcelona
To: kde-core-devel@...
Message-ID: <200911091722.02201.notmart@...>
Content-Type: Text/Plain;  charset="iso-8859-1"

On Sunday 08 November 2009, Albert Astals Cid wrote:
> A Diumenge, 8 de novembre de 2009, Inge Wallin va escriure:
> > On Sunday 08 November 2009 20:56:20 Albert Astals Cid wrote:
> > > A Diumenge, 8 de novembre de 2009, Frank Karlitschek va escriure:
> > > > Hi,
> > > >
> > > > as a favor for Quim Gil from Maemo I forward two things to you which
> > > > might be interesting.
> > > >
> > > >
> > > > 1. The Maemo people are doing a "UX meets Code" Hackfest in Barcelona
> > > > in December.
> > > > All KDE people are invited. Please see this page if you are
> > > > interested to participate.
> > > > http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend
> > > >
> > > >
> > > > 2. Quim is looking for developers to help with a Qt 4.6 based chess
> > > > game for Maemo.
> > > > Check this page if you want to help:
> > > > http://wiki.maemo.org/Miniature
> > >
> > > You want kde-games-devel@... for KDE games developers, but not sure
> > >  people there is interested in doing Qt/Maemo development, since it's
> > >  really not KDE development after all.
> >
> > I think this reasoning is wrong.  KDE is not just the desktop environment
> >  any more, it's the toolkit, including kdelibs and the community.
> > Nowadays KDE applications are cross platform, and the more we can get
> > into the mobile devices and make our apps run on small form factors the
> > better.
> >
> > Development for Maemo is just our next frontier.
>
> We disagree here :-)
>
> As part of the KDE community I care the less for Maemo until it ships KDE,
>  it shipping Qt is cool because means i have knowledge to code for it if i
>  feel like, it gives me more job opportunities, and probably creates more

well, the opportunity for Maemo to ship KDE should also be created, if we
don't push it i doubt that will happen any day, if we show that using kdelibs
there besides Qt can have clear advantage could instead make it happen, and
being on a potentially successful smartphone platform is indeed -very-
interesting

Cheers,
Marco Martin


------------------------------

Message: 3
Date: Mon, 09 Nov 2009 19:57:12 +0100
From: Sebastian Trueg <trueg@...>
Subject: Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to
       trig
To: kde-core-devel@...
Message-ID: <4AF86608.6020801@...>
Content-Type: text/plain; charset=ISO-8859-1

Abhinav Chaturvedi wrote:
> Hi Sebastian,
> I cannot seem to find which version of libredland and libraptor I have.
> But what I can tell you is that I downloaded Soprano-2.3.1 and compiled
> it into /usr/local.

redland-config --version
should help here.

> It is this Soprano that I then used during kdebase compilation. I was
> compiling KDE-4.3.3 on an OpenSuse-11.1 system (which has KDE-4.1.x).
> For now, I have managed to compile kdebase by disabling Nepomuk
> compilation (BUILD_nepomuk:BOOL=OFF in CMakeCache.txt).

Could you get the cmake output from your own Soprano compilation to me?

> I don't know whether there is any connection between Soprano and
> Nepomuk. So, i don't know whether you can infer redland and raptor
> versions from the Soprano version number.

Nepomuk is based on Soprano.

> But if you could tell me of a way to find the redland and raptor
> versions, then I'll hurry the answers back to you.
>
> Thanks for your help
> Abhinav.
>
> 2009/11/5 <kde-core-devel-request@...
> <mailto:kde-core-devel-request@...>>
>
>     Send kde-core-devel mailing list submissions to
>            kde-core-devel@... <mailto:kde-core-devel@...>
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>            https://mail.kde.org/mailman/listinfo/kde-core-devel
>     or, via email, send a message with subject or body 'help' to
>            kde-core-devel-request@...
>     <mailto:kde-core-devel-request@...>
>
>     You can reach the person managing the list at
>            kde-core-devel-owner@...
>     <mailto:kde-core-devel-owner@...>
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of kde-core-devel digest..."
>
>
>     Today's Topics:
>
>       1. Re: Qt KDE integration in kdereview. (Diego Iastrubni)
>       2. Re: Attica moved to kdereview (Frederik Gladhorn)
>       3. Re: device-automounter moved to kdereview (Albert Astals Cid)
>       4. Re: Bugreporting barrier is too low with the new Dr. Konqi
>          (Dar?o Andr?s)
>       5. Re: [newbie]: Problems compiling kdebase-4.3 due to trig
>          (Sebastian Tr?g)
>       6. Re: Qt KDE integration in kdereview. (Olivier Goffart)
>       7. Re: KDE is not an OS platform... (And neither is Gnome)
>          (Alexander Neundorf)
>       8. Re: Qt KDE integration in kdereview. (Alexander Neundorf)
>       9. Re: Rocs moved to kdereview. (Tomaz Canabrava)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Wed, 4 Nov 2009 21:07:11 +0200
>     From: Diego Iastrubni <elcuco@... <mailto:elcuco@...>>
>     Subject: Re: Qt KDE integration in kdereview.
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042107.11986.elcuco@...
>     <mailto:200911042107.11986.elcuco@...>>
>     Content-Type: Text/Plain;  charset="iso-8859-1"
>
>     On Tuesday 03 November 2009 21:11:21 David Faure wrote:
>     > On Tuesday 03 November 2009, Diego Iastrubni wrote:
>     > > On Tuesday 03 November 2009 17:55:51 Olivier Goffart wrote:
>     > > > Hello.
>     > > >
>     > > > I have just submitted a new plugin in kdereview:
>     > > > qguiplatformplugin_kde
>     > > >
>     > > > The objective of this plugin is to allow pure Qt Application
>     (not KDE
>     > > > ones) to get better integration into KDE.
>     > >
>     > > How about integrating KDE widgets directly into pure Qt
>     applications?
>     > >
>     > > I see that QMainWindow::menuBar(), QMainWindow::statusBar() and
>     > > QMainWindow::addToolBar(QString) can be hacked. Maybe that
>     plugin can
>     > >  provide the menu/statusbar/toolbar "virtual constructors" or
>     something.
>     >
>     > You mean in order to create KMainWindows and KToolBars?
>     > What would this provide to the Qt applications?
>     making a KMainWindow, from a QMainWindow should be difficult.
>     However, one of
>     the most missing features for me in QToolBars are the icon/text
>     settings and
>     the lock toolbars command.
>
>     I am just thinking aloud: how hard can this be?
>
>
>
>     ------------------------------
>
>     Message: 2
>     Date: Wed, 04 Nov 2009 20:12:06 +0100
>     From: Frederik Gladhorn <gladhorn@... <mailto:gladhorn@...>>
>     Subject: Re: Attica moved to kdereview
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <4af1d3da.0f1abc0a.68f4.3f25@...
>     <mailto:4af1d3da.0f1abc0a.68f4.3f25@...>>
>     Content-Type: text/plain; charset="ISO-8859-1"
>
>     Hola Albert,
>     thanks a lot for the review!
>     I hope that we addressed your points by now.
>
>     Albert Astals Cid wrote:
>     > A Dimarts, 3 de novembre de 2009, Frederik Gladhorn va escriure:
>     >> Hi all,
>     >> after spending some time with libattica, we decided that now is a
>     good
>     >>  point to get a review for it and eventually have it used in KDE.
>     >
>     > The licensing is unclear, activity.h is GPL2+ while downloaditem.h is
>     > LGPL2+
>     Done, we forgot to make it the same everywhere, it's relicensed to
>     LGPL2+ in
>     agreement with all authors now.
>
>     > You have one foreach without const & in the "iterator"
>     /me hides :D
>
>     > Maybe it would make sense to d-pointify Attica:BaseJob::Metadata,
>     > Attica::DownloadUrlDescription, Attica::GetJob, Attica::PostJob
>     Mostly done, will be finished tomorrow.
>
>     > In Attica::DownloadUrlDescription if you put the two bools
>     together your
>     > struct will use less memory
>     Done.
>     > Should downloadUrlDescription(), previewPicture(), license(),
>     author() of
>     > Attica::Content be const?
>     Done.
>     > Should url() in Attica::DownloadItem be const?
>     Yes.
>     > Any reason to make Attica::DownloadItem use a
>     > QExplicitlySharedDataPointer?
>     Total nonsense and an oversight by me.
>     Seems like I wasn't quite awake when writing that class...
>
>     > From the application point of view, it would make sense to me that
>     if for
>     > example it makes no sense that the application ever calls
>     > Folder::setMessageCount it should be private and called by a
>     friend class.
>     > But maybe it makes sense calling Folder::setMessageCount and it's
>     ok :D
>     Since we support creating items and sending them to the server
>     again, most
>     setters make sense. The case you asked about is indeed questionable.
>
>     >
>     > After a quick look at the API i'm not sure if the Jobs are
>     supposed to be
>     > part of the public API or not. Their headers are installed an the
>     classes
>     > exported, but
>     >
>     > GetJob(const QSharedPointer<Internals>& internals, const
>     QNetworkRequest&
>     > request);
>     > seems a bit weird, what's that QSharedPointer<Internals>?
>     >
>     Yep, this is supposed to be used only internally. You just get
>     instances of
>     these classes back from Attica::Provider. Constructors changed to
>     private or
>     protected now.
>
>     Thanks!
>
>     Greetings
>     Frederik
>
>
>     ------------------------------
>
>     Message: 3
>     Date: Wed, 4 Nov 2009 20:41:56 +0100
>     From: Albert Astals Cid <aacid@... <mailto:aacid@...>>
>     Subject: Re: device-automounter moved to kdereview
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042041.56630.aacid@...
>     <mailto:200911042041.56630.aacid@...>>
>     Content-Type: Text/Plain;  charset="iso-8859-15"
>
>     A Dimecres, 4 de novembre de 2009, Trever Fischer va escriure:
>     > On Tuesday 03 November 2009 6:18:43 pm Albert Astals Cid wrote:
>     > > A Dimarts, 3 de novembre de 2009, Jacopo De Simoi va escriure:
>     > > > On Tuesday 03 November 2009 02:15:20 Trever Fischer wrote:
>     > > > > On Monday 02 November 2009 6:45:18 pm Jacopo De Simoi wrote:
>     > > > > > On Monday 02 November 2009 23:56:14 Jacopo De Simoi wrote:
>     > > > > > > > So you /don't / have to use UDIs (unless you're
>     manually adding
>     > > > > > > > to the list) to use the feature.
>     > > > > > >
>     > > > > > > I believe we need to get rid of the UDIs and provide
>     some more
>     > > > > > > not just user-friendly, but "human-friendly" strings..
>     Having to
>     > > > > > > deal with them even in some cases is not really
>     acceptable. I'll
>     > > > > > > try to have a look into this to see how we can sort this out
>     > > > > >
>     > > > > > Just quickly playing with the solid minibrowser I have a few
>     > > > > > suggestions
>     > > > > >
>     > > > > > First of all, show whichever icon solids give to the
>     device, it
>     > > > > > really really helps to figure out what we are talking
>     about even
>     > > > > > before we start reading.
>     > > > > >
>     > > > > > The volume property info.product is quite uninformative
>     (usually
>     > > > > >  Volume(ext3)), but if you jump back to the closest
>     relative which
>     > > > > > has a info.product property you will find quite
>     interesting things,
>     > > > > > such as ExpressCard, or stuff like that.
>     > > > > >
>     > > > > > Then I'd compose a string with the following field (with
>     parent I
>     > > > > > mean the closest device in the hierarchy which has the infos
>     > > > > > required)
>     > > > > >
>     > > > > > parent.info.vendor parent.info.product volume.info.product
>     (size)
>     > > > > > Some real-life examples:
>     > > > > >
>     > > > > > Seagate FreeAgent Go Backup_HD (160 Go)
>     > > > > > ST325082 0A MediaHD (250 Go)
>     > > > > > Lexar ExpressCard ssdhome (5 Go)
>     > > > > > Lexar ExpressCard ssdroot (3 Go)
>     > > > > > SD02G Volume (ext3) (2 Go) (with SD icon)
>     > > > > > Kingston FCR-HS219/1 MicroSD (2 Go) (I'm cheating here...
>     MicroSD
>     > > > > > is the volume label)
>     > > > > >
>     > > > > > Still, as you can see there's room for improvement, in
>     particular
>     > > > > > the second guy was giving quite debatable information
>     about itself
>     > > > > > (however still better than
>     > > > > > /org/freedesktop/Hal/devices/volume_uuid_ECBF_30CC)
>     > > > >
>     > > > > Nonetheless a good idea. I added it to the GUI.
>     > > >
>     > > > Ok, now this looks much better; what about this, now, to make
>     it look
>     > > > even better;
>     > > >
>     > > > If (and only if) there exists more than one volume with the same
>     > > > parent, group them with the parent; then the parent will be
>     shown with
>     > > > vendor() and product() and total size (should be available with
>     > > >  storage.removable.media_size) and then each child (partition)
>     would
>     > > > just show description() and size This is visually better since it
>     > > > removes redundant information for partitions of the same
>     drive. and
>     > > > makes it easier to browse.
>     > > >
>     > > > On the other hand, if a volume is an only child, then don't
>     add another
>     > > >  node and use the long description we talked about yesterday.
>     > > >
>     > > > Also, imho the informations should be refreshed even if it's
>     already
>     > > >  present in the .rc file whenever possible; besides; who is
>     responsible
>     > > > to fill in the devices in the .rc file? the daemon I suppose;
>     would it
>     > > > be possible to save the pretty name we have found for our
>     device at the
>     > > > daemon level? so that whenever you connect the drive, the user
>     would
>     > > > find it with its pretty name in the disconnected devices node
>     as well.
>     > > > Having it set up at the daemon level could make the kcm part
>     merely
>     > > > read it from the .rc since it will be automagically updated.
>     > > >
>     > > > Moreover, I believe that the Add device button is useless;
>     nobody would
>     > > >  really enter the udi of a device.
>     > >
>     > > I agree here, and the forget device is not of much use either
>     >
>     > The reason I put it in was I figured there needs to be some way to
>     undo the
>     > otherwise permanent memorization of "automount this device because
>     it has
>     >  been mounted before".
>     >
>     > > > Nice job!
>     > > > @Albert, what  do you think about the ui fixes?
>     > >
>     > > The list let's you do multiple selection, i don't think that
>     makes much
>     > >  sense. Also i tried to change Automount on login and Automount
>     on attach
>     > >  from No to Yes on my pendrive but wasn't able to do it.
>     >
>     > Multiple selection lets you forget more than one device at a time.
>     Also,
>     >  those two fields only change when the device list is rebuilt. I'm
>     thinking
>     >  I should build a model specifically for the KCM so that the
>     updating of
>     >  this is done when the checkboxes are toggled, and it'd be a lot
>     cleaner
>     >  than just a qstandardmodel.
>
>     Ok, makes sense, thanks for the clarification.
>
>     Albert
>
>     >
>     > > Albert
>     >
>
>
>
>     ------------------------------
>
>     Message: 4
>     Date: Wed, 4 Nov 2009 17:14:03 -0300
>     From: Dar?o Andr?s <andresbajotierra@...
>     <mailto:andresbajotierra@...>>
>     Subject: Re: Bugreporting barrier is too low with the new Dr. Konqi
>     To: KDE-Devel <kde-core-devel@... <mailto:kde-core-devel@...>>
>     Message-ID:
>            <a2c126ef0911041214n5613e97cv2ff945f1994cb28f@...
>     <mailto:a2c126ef0911041214n5613e97cv2ff945f1994cb28f@...>>
>     Content-Type: text/plain; charset=ISO-8859-1
>
>     Ok, I have currently implemented some features in order to improve the
>     situation:
>
>     - The duplicate list that DrKonqi provides should be smarter and a bit
>     smaller (as it uses a stricter query to bugzilla)
>     - The duplicate list now includes the bug status in a tag, with
>     no-jargon (ex ."[Open]", "[Fixed]", "[Already Reported]", "[Invalid]")
>     - When you want to open a possible duplicate report, if that report
>     "X" is already marked as duplicate of another report "Z", you can
>     choose to show the report you wanted to open ("X") or the main report
>     ("Z") <- Resolving nested duplicate levels
>
>     Other fixes that I have coded but I haven't commited yet:
>
>     - If there are possible duplicates listed and the user didn't selected
>     anyone, nor marked anyone to attach the new information to it, a
>     messagebox will appear asking if he is sure.
>
>     - In the description step, if the user haven't entered a proper amount
>     of input, the user is *forced* to do so (we need to discuss the amount
>     of characters to be considered good input) (the user already selected
>     the checkbox "I can provide information about the crash"). If the user
>     doesn't accept this, the dialog is closed (but a warning about the
>     dialog being closed appears, if the user changes his/her mind...)
>
>     In both messages I'm explicitly saying that not following this advices
>     will *waste* the time of the KDE developers and triagers, so at least
>     they can think a bit before sending pseudo-crap. (yes, the text needs
>     to be improved, may be it is too harsh...)
>
>     Screenshots of earlier implementation of this features:
>
>     http://imagebin.ca/view/XY3uu1W.html
>     http://imagebin.ca/view/i2-0cQ.html
>     http://imagebin.ca/view/0jSX7VP.html
>
>     I would like to get some feedback about all this things
>
>     Thanks in advance.
>     Regards
>
>     Dar?o A.
>
>
>     ------------------------------
>
>     Message: 5
>     Date: Wed, 4 Nov 2009 21:32:09 +0100
>     From: Sebastian Tr?g <trueg@... <mailto:trueg@...>>
>     Subject: Re: [newbie]: Problems compiling kdebase-4.3 due to trig
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042132.09880.trueg@...
>     <mailto:200911042132.09880.trueg@...>>
>     Content-Type: Text/Plain;  charset="iso-8859-15"
>
>     which version of libredland and libraptor do you have installed?
>
>     On Tuesday 03 November 2009 22:58:14 Abhinav Chaturvedi wrote:
>     > Hi all,
>     >
>     > I am having problems compiling kdebase (of KDE-4.3 branch) and its
>     seems to
>     > because of nepomuk.
>     > i downloaded soprano-2.3.1 from sourceforge.net
>     <http://sourceforge.net>, compiled it and installed
>     > it in /usr/local.
>     > Hence, when I do cmakekde in kdebase, I get the following message:
>     >
>     >
>     > Found Soprano Plugin Dir: /usr/local/share/soprano/
>     > plugins/soprano/plugins
>     > -- Found Soprano Plugins: nquadparser nquadserializer raptorparser
>     > raptorserializer redlandbackend sesame2backend
>     >
>     > There is no 'trig'. I am assuming there should be a parser for it like
>     >  there are for raptor, redland etc.
>     > And that this parser should have been included in Soprano-2.3.1. But
>     > apparently it is not. Which is why
>     > I get the following message when compiling kdebase.
>     >
>     > [ 10%] Generating nie.h,
>     > nie.cpp
>     >
>     > Could not find parser plugin for encoding
>     > trig
>     >
>     > make[2]: *** [runtime/nepomuk/strigibackend/nie.h] Error
>     > 1
>     > make[1]: ***
>     > [runtime/nepomuk/strigibackend/CMakeFiles/sopranobackend.dir/all]
>     Error
>     > 2
>     > make[1]: *** Waiting for unfinished
>     > jobs....
>     >
>     > Linking CXX executable
>     > knotify4
>     >
>     > [ 10%] Built target
>     > knotify
>     >
>     > make: *** [all] Error 2
>     >
>     >
>     > I was wondering if you have seen this problem before. I must tell
>     you that
>     >  I did *not* checkout anything other
>     > than kdepimlibs, kdebase, kdelibs and phonon. These were enough when I
>     >  tried compiling KDE-4.3 some
>     > months back.
>     >
>     > Is there anyway in which I can bypass 'nepomuk' compilation
>     altogether?
>     > If not, then how can I solve the above problem? Do I need to
>     checkout some
>     > other KDE packages?
>     >
>     > Thanks for your help
>     > Abhinav.
>     >
>
>
>     ------------------------------
>
>     Message: 6
>     Date: Wed, 4 Nov 2009 22:33:21 +0200
>     From: Olivier Goffart <ogoffart@... <mailto:ogoffart@...>>
>     Subject: Re: Qt KDE integration in kdereview.
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042133.21442.ogoffart@...
>     <mailto:200911042133.21442.ogoffart@...>>
>     Content-Type: Text/Plain;  charset="iso-8859-1"
>
>     Le Wednesday 04 November 2009, Diego Iastrubni a ?crit :
>
>     > making a KMainWindow, from a QMainWindow should be difficult.
>     However, one
>     >  of the most missing features for me in QToolBars are the icon/text
>     >  settings and the lock toolbars command.
>     >
>     > I am just thinking aloud: how hard can this be?
>
>     Regarding the icon/text settings in a QToolBar:
>     - The default icon size is read from the KDE config for the default
>     KDE icon
>     size in toolba
>     - The default text position is read from the KDE config if using
>     Qt::ToolButtonFollowStyle  as QToolBar::toolButtonStyle  (new in
>     4.6, we could
>     not make it the default because it was a too huge behaviour change)
>
>     There is currently no plan to support being able to edit QToolBar as
>     KDE does.
>
>
>
>     ------------------------------
>
>     Message: 7
>     Date: Wed, 4 Nov 2009 21:53:25 +0100
>     From: Alexander Neundorf <neundorf@... <mailto:neundorf@...>>
>     Subject: Re: KDE is not an OS platform... (And neither is Gnome)
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042153.25201.neundorf@...
>     <mailto:200911042153.25201.neundorf@...>>
>     Content-Type: text/plain;  charset="iso-8859-1"
>
>     On Wednesday 04 November 2009, David Faure wrote:
>     > On Wednesday 04 November 2009, nf2 wrote:
>     > > * But Qt-only apps?
>     > >
>     > > And i do believe Qt is quite important for getting more apps written
>     > > for the FOSS desktop. As its portability is very attractive.
>     >
>     > OK, that's a good point. However QFile/QDir is not the answer IMHO.
>     > Qt has a nice API for async networking requests already:
>     > QNetworkAccessManager (for which we have a KIO backend; the qt-kde
>     platform
>     > plugin (cf the thread from Olivier) could even use that when
>     kdelibs is
>     > around).
>     > But for file dialogs, it misses directory listing, and stat, at least.
>
>     I think QAbstractFileEngine comes quite close, you can use to to plug
>     in "virtual" filesystems based on URLs into Qt apps, including the file
>     dialog.
>
>     Alex
>
>
>     ------------------------------
>
>     Message: 8
>     Date: Wed, 4 Nov 2009 21:59:54 +0100
>     From: Alexander Neundorf <neundorf@... <mailto:neundorf@...>>
>     Subject: Re: Qt KDE integration in kdereview.
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID: <200911042159.54853.neundorf@...
>     <mailto:200911042159.54853.neundorf@...>>
>     Content-Type: text/plain;  charset="iso-8859-1"
>
>     On Wednesday 04 November 2009, David Faure wrote:
>     > On Wednesday 04 November 2009, George Kiagiadakis wrote:
>     > > On Wed, Nov 4, 2009 at 3:19 AM, David Faure <faure@...
>     <mailto:faure@...>> wrote:
>     > > > On Wednesday 04 November 2009, Michael Pyne wrote:
>     > > >> On Tuesday 03 November 2009 17:10:19 Kevin Krammer wrote:
>     > > >> > Maybe startkde could set KDEHOME to localprefix if it is
>     not set
>     > > >> > yet?
>     > > >>
>     > > >> That wouldn't be a bad idea either, it's easier just to
>     always have
>     > > >> KDEHOME set than special-casing it.
>     > > >
>     > > > Yep, excellent idea.
>     > >
>     > > No, bad idea. If you are using both kde3 and kde4 apps and you want
>     > > them to use different KDEHOMEs, setting KDEHOME in startkde is just
>     > > going to force them both to use the same KDEHOME, which is not
>     what we
>     > > want.
>     >
>     > True.
>     > And I just realized that it wouldn't help making sure KDEHOME is
>     always
>     > set, since one can also run kde apps outside of a kde workspace (-> no
>     > startkde run).
>     >
>     > > That's why the KDE4_DEFAULT_HOME cmake variable exists.
>     >
>     > Yeah but that's not introspectable.
>     > Hmm, actually, it is:  `kde4-config --localprefix`, but calling a
>     process
>     > probably too slow for doing from Qt?
>
>     Hmm, if it's done once on application startup it might be acceptable.
>
>     It's also saved in
>     share/apps/cmake/modules/KDELibsDependencies.cmake, in the
>     KDE_DEFAULT_HOME variable.
>     You can basically rely on the format of that line:
>     set(KDE_DEFAULT_HOME ".kde")
>     So without really parsing it just matching a regexp should do.
>
>     Alex
>
>
>     ------------------------------
>
>     Message: 9
>     Date: Wed, 4 Nov 2009 20:48:04 -0200
>     From: Tomaz Canabrava <tumaix@... <mailto:tumaix@...>>
>     Subject: Re: Rocs moved to kdereview.
>     To: kde-core-devel@... <mailto:kde-core-devel@...>
>     Message-ID:
>            <7ebbb4b50911041448g42da8498gf938ec5aae8436f8@...
>     <mailto:7ebbb4b50911041448g42da8498gf938ec5aae8436f8@...>>
>     Content-Type: text/plain; charset=ISO-8859-1
>
>     Ok, I'v managed to fix 2 crashes, workarounding a well known
>     qt-problem on trees & graphicsview.
>     it shoudn't crash no more.
>
>     and improved the showing of the properties of the nodes and edges.
>
>     tomorrow I will do nothing ( beach time ), but I plan to have
>     everything that anyone say here fixed by next sunday.
>
>
>     ------------------------------
>
>     _______________________________________________
>     kde-core-devel mailing list
>     kde-core-devel@... <mailto:kde-core-devel@...>
>     https://mail.kde.org/mailman/listinfo/kde-core-devel
>
>
>     End of kde-core-devel Digest, Vol 80, Issue 27
>     **********************************************
>
>
>
>
> --
> It's the peoples' will, I am their leader, I must follow them. (Jim
> Hacker in Yes Minister)


------------------------------

_______________________________________________
kde-core-devel mailing list
kde-core-devel@...
https://mail.kde.org/mailman/listinfo/kde-core-devel


End of kde-core-devel Digest, Vol 80, Issue 43
**********************************************



--
It's the peoples' will, I am their leader, I must follow them. (Jim Hacker in Yes Minister)

# This is the CMakeCache file.
# For build in directory: /home/kde-devel/Download/soprano-2.3.1/build
# It was generated by CMake: /usr/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUI's for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Path to a file.
CLUCENE_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
CLUCENE_LIBRARY:FILEPATH=/usr/lib/libclucene.so

//Path to a file.
CLUCENE_LIBRARY_DIR:PATH=/usr/lib

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
// CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.
CMAKE_BUILD_TYPE:STRING=

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler.
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release minsize builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g

//C compiler.
CMAKE_C_COMPILER:FILEPATH=/usr/bin/gcc

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release minsize builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/home/kde-devel/kde/installs/4.3

//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip

//If true, cmake will use relative paths in makefiles and projects.
CMAKE_USE_RELATIVE_PATHS:BOOL=OFF

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE

//Enable to build Debian packages
CPACK_BINARY_DEB:BOOL=OFF

//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=OFF

//Enable to build RPM packages
CPACK_BINARY_RPM:BOOL=OFF

//Enable to build STGZ packages
CPACK_BINARY_STGZ:BOOL=ON

//Enable to build TBZ2 packages
CPACK_BINARY_TBZ2:BOOL=ON

//Enable to build TGZ packages
CPACK_BINARY_TGZ:BOOL=ON

//Enable to build TZ packages
CPACK_BINARY_TZ:BOOL=ON

//Enable to build TBZ2 source packages
CPACK_SOURCE_TBZ2:BOOL=ON

//Enable to build TGZ source packages
CPACK_SOURCE_TGZ:BOOL=ON

//Enable to build TZ source packages
CPACK_SOURCE_TZ:BOOL=ON

//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=OFF

//The subdirectory to the header prefix
INCLUDE_INSTALL_DIR:PATH=/home/kde-devel/kde/installs/4.3/include

//Path to a file.
JAVA_AWT_INCLUDE_PATH:PATH=/usr/lib/jvm/java/include

//Path to a library.
JAVA_AWT_LIBRARY:FILEPATH=/usr/lib/jvm/java/jre/lib/i386/libjawt.so

//Path to a file.
JAVA_INCLUDE_PATH:PATH=/usr/lib/jvm/java/include

//Path to a file.
JAVA_INCLUDE_PATH2:PATH=/usr/lib/jvm/java/include/linux

//Path to a library.
JAVA_JVM_LIBRARY:FILEPATH=/usr/lib/jvm/java/jre/lib/i386/client/libjvm.so

//Library directory name
LIB_DESTINATION:STRING=/home/kde-devel/kde/installs/4.3/lib

//Define suffix of directory name (32/64)
LIB_SUFFIX:STRING=

//Base directory for pkgconfig files
PKGCONFIG_INSTALL_PREFIX:STRING=/home/kde-devel/kde/installs/4.3/lib/pkgconfig/

//Path to a program.
QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/qdbuscpp2xml

//Path to a program.
QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/qdbusxml2cpp

//The location of the Qt docs
QT_DOC_DIR:PATH=/home/kde-devel/kde-qt/doc

QT_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include

//Qt library dir
QT_LIBRARY_DIR:PATH=/home/kde-devel/kde-qt/lib

//The location of the Qt mkspecs
QT_MKSPECS_DIR:PATH=/home/kde-devel/kde-qt/mkspecs

//The moc executable
QT_MOC_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/moc

//The location of the Qt plugins
QT_PLUGINS_DIR:PATH=/home/kde-devel/kde-qt/plugins

//Path to a program.
QT_QMAKE_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/qmake

//Path to a file.
QT_QT3SUPPORT_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/Qt3Support

//Path to a library.
QT_QT3SUPPORT_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQt3Support.so

//Path to a file.
QT_QTASSISTANT_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtAssistant

//Path to a library.
QT_QTASSISTANT_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtAssistantClient.so

//Path to a file.
QT_QTCORE_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtCore

//Path to a library.
QT_QTCORE_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtCore.so

//Path to a file.
QT_QTDBUS_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtDBus

//Path to a library.
QT_QTDBUS_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtDBus.so

//Path to a file.
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtDesigner

//Path to a library.
QT_QTDESIGNERCOMPONENTS_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtDesignerComponents.so

//Path to a file.
QT_QTDESIGNER_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtDesigner

//Path to a library.
QT_QTDESIGNER_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtDesigner.so

//Path to a file.
QT_QTGUI_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtGui

//Path to a library.
QT_QTGUI_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtGui.so

//Path to a file.
QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND

//Path to a library.
QT_QTMOTIF_LIBRARY:FILEPATH=QT_QTMOTIF_LIBRARY-NOTFOUND

//Path to a file.
QT_QTNETWORK_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtNetwork

//Path to a library.
QT_QTNETWORK_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtNetwork.so

//Path to a file.
QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND

//Path to a library.
QT_QTNSPLUGIN_LIBRARY:FILEPATH=QT_QTNSPLUGIN_LIBRARY-NOTFOUND

//Path to a file.
QT_QTOPENGL_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtOpenGL

//Path to a library.
QT_QTOPENGL_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtOpenGL.so

//Path to a file.
QT_QTSCRIPT_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtScript

//Path to a library.
QT_QTSCRIPT_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtScript.so

//Path to a file.
QT_QTSQL_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtSql

//Path to a library.
QT_QTSQL_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtSql.so

//Path to a file.
QT_QTSVG_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtSvg

//Path to a library.
QT_QTSVG_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtSvg.so

//Path to a file.
QT_QTTEST_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtTest

//Path to a library.
QT_QTTEST_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtTest.so

//Path to a file.
QT_QTUITOOLS_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtUiTools

//Path to a library.
QT_QTUITOOLS_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtUiTools.a

//Path to a file.
QT_QTXML_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/QtXml

//Path to a library.
QT_QTXML_LIBRARY:FILEPATH=/home/kde-devel/kde-qt/lib/libQtXml.so

//Path to a file.
QT_QT_INCLUDE_DIR:PATH=/home/kde-devel/kde-qt/include/Qt

//Path to a program.
QT_RCC_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/rcc

//Path to a program.
QT_UIC3_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/uic3

//The uic executable
QT_UIC_EXECUTABLE:FILEPATH=/home/kde-devel/kde-qt/bin/uic

//Path to a program.
RAPTOR_CONFIG:FILEPATH=/usr/bin/raptor-config

//Path to a file.
RAPTOR_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
RAPTOR_LIBRARIES:FILEPATH=/usr/lib/libraptor.so

//Path to a program.
RASQAL_CONFIG:FILEPATH=/usr/bin/rasqal-config

//Path to a file.
RASQAL_INCLUDE_DIR:PATH=/usr/include/rasqal/rasqal

//Path to a library.
RASQAL_LIBRARIES:FILEPATH=/usr/lib/librasqal.so

//Path to a program.
REDLAND_CONFIG:FILEPATH=/usr/bin/redland-config

//Path to a file.
REDLAND_INCLUDE_DIR:PATH=/usr/include/redland

//Path to a library.
REDLAND_LIBRARIES:FILEPATH=/usr/lib/librdf.so

//Build the Soprano API documentation
SOPRANO_BUILD_API_DOCS:BOOL=OFF

//Build all unit tests
SOPRANO_BUILD_TESTS:BOOL=OFF

//Disable the compilation of the clucene-based full-text index
SOPRANO_DISABLE_CLUCENE_INDEX:BOOL=OFF

//Disable the D-Bus integration
SOPRANO_DISABLE_DBUS:BOOL=OFF

//Disable the compilation of the raptor parser and serializer plugins
// (provides most Soprano parsers and serializers)
SOPRANO_DISABLE_RAPTOR_PARSER:BOOL=OFF

//Disable the compilation of the redland backend
SOPRANO_DISABLE_REDLAND_BACKEND:BOOL=OFF

//Disable the compilation of the sesame2 backend
SOPRANO_DISABLE_SESAME2_BACKEND:BOOL=OFF

//Path to a file.
X11_ICE_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_ICE_LIB:FILEPATH=/usr/lib/libICE.so

//Path to a library.
X11_SM_LIB:FILEPATH=/usr/lib/libSM.so

//Path to a file.
X11_X11_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_X11_LIB:FILEPATH=/usr/lib/libX11.so

//Path to a file.
X11_XShm_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_XTest_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_XTest_LIB:FILEPATH=/usr/lib/libXtst.so

//Path to a file.
X11_Xaccessrules_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xaccessstr_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xau_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xau_LIB:FILEPATH=/usr/lib/libXau.so

//Path to a file.
X11_Xcomposite_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcomposite_LIB:FILEPATH=/usr/lib/libXcomposite.so

//Path to a file.
X11_Xcursor_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcursor_LIB:FILEPATH=/usr/lib/libXcursor.so

//Path to a file.
X11_Xdamage_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xdamage_LIB:FILEPATH=/usr/lib/libXdamage.so

//Path to a file.
X11_Xdmcp_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xdmcp_LIB:FILEPATH=/usr/lib/libXdmcp.so

//Path to a library.
X11_Xext_LIB:FILEPATH=/usr/lib/libXext.so

//Path to a file.
X11_Xfixes_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xfixes_LIB:FILEPATH=/usr/lib/libXfixes.so

//Path to a file.
X11_Xft_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xft_LIB:FILEPATH=/usr/lib/libXft.so

//Path to a file.
X11_Xinerama_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinerama_LIB:FILEPATH=/usr/lib/libXinerama.so

//Path to a file.
X11_Xinput_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinput_LIB:FILEPATH=/usr/lib/libXi.so

//Path to a file.
X11_Xkb_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xkblib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xlib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xpm_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xpm_LIB:FILEPATH=/usr/lib/libXpm.so

//Path to a file.
X11_Xrandr_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrandr_LIB:FILEPATH=/usr/lib/libXrandr.so

//Path to a file.
X11_Xrender_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrender_LIB:FILEPATH=/usr/lib/libXrender.so

//Path to a file.
X11_Xscreensaver_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xscreensaver_LIB:FILEPATH=/usr/lib/libXss.so

//Path to a file.
X11_Xshape_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xt_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xt_LIB:FILEPATH=/usr/lib/libXt.so

//Path to a file.
X11_Xutil_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xv_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xv_LIB:FILEPATH=/usr/lib/libXv.so

//Path to a library.
X11_Xxf86misc_LIB:FILEPATH=/usr/lib/libXxf86misc.so

//Path to a file.
X11_dpms_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86misc_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86vmode_INCLUDE_PATH:PATH=/usr/include

//Value Computed by CMake
nquads_parser_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/parsers/nquads

//Value Computed by CMake
nquads_parser_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/parsers/nquads

//Value Computed by CMake
nquads_serializer_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/serializers/nquads

//Value Computed by CMake
nquads_serializer_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/serializers/nquads

//Value Computed by CMake
soprano_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build

//Dependencies for the target
soprano_LIB_DEPENDS:STATIC=general;/home/kde-devel/kde-qt/lib/libQtCore.so;general;-lpthread;

//Value Computed by CMake
soprano_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1

//Value Computed by CMake
soprano_backends_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/backends

//Value Computed by CMake
soprano_backends_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/backends

//Value Computed by CMake
soprano_core_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/soprano

//Value Computed by CMake
soprano_core_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/soprano

//Value Computed by CMake
soprano_includes_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/includes

//Value Computed by CMake
soprano_includes_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/includes

//Dependencies for the target
soprano_nquadparser_LIB_DEPENDS:STATIC=general;soprano;

//Dependencies for the target
soprano_nquadserializer_LIB_DEPENDS:STATIC=general;soprano;

//Value Computed by CMake
soprano_parsers_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/serializers

//Value Computed by CMake
soprano_parsers_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/serializers

//Value Computed by CMake
soprano_raptor_parser_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/parsers/raptor

//Value Computed by CMake
soprano_raptor_parser_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/parsers/raptor

//Value Computed by CMake
soprano_raptor_serializer_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/serializers/raptor

//Value Computed by CMake
soprano_raptor_serializer_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/serializers/raptor

//Dependencies for the target
soprano_raptorparser_LIB_DEPENDS:STATIC=general;soprano;general;/usr/lib/libraptor.so;

//Dependencies for the target
soprano_raptorserializer_LIB_DEPENDS:STATIC=general;soprano;general;soprano_redlandcore;general;/usr/lib/libraptor.so;

//Value Computed by CMake
soprano_redland_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/backends/redland

//Value Computed by CMake
soprano_redland_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/backends/redland

//Dependencies for the target
soprano_redlandbackend_LIB_DEPENDS:STATIC=general;soprano_redlandcore;

//Dependencies for the target
soprano_redlandcore_LIB_DEPENDS:STATIC=general;soprano;general;/usr/lib/librdf.so;

//Value Computed by CMake
soprano_rules_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/rules

//Value Computed by CMake
soprano_rules_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/rules

//Value Computed by CMake
soprano_server_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/server

//Value Computed by CMake
soprano_server_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/server

//Value Computed by CMake
soprano_server_dbus_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/server/dbus

//Value Computed by CMake
soprano_server_dbus_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/server/dbus

//Value Computed by CMake
soprano_sesame2_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/backends/sesame2

//Value Computed by CMake
soprano_sesame2_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/backends/sesame2

//Dependencies for the target
soprano_sesame2backend_LIB_DEPENDS:STATIC=general;soprano;general;/usr/lib/jvm/java/jre/lib/i386/client/libjvm.so;

//Value Computed by CMake
soprano_tools_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/tools

//Value Computed by CMake
soprano_tools_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/tools

//Dependencies for the target
sopranoclient_LIB_DEPENDS:STATIC=general;soprano;general;/home/kde-devel/kde-qt/lib/libQtCore.so;general;-lpthread;general;/home/kde-devel/kde-qt/lib/libQtNetwork.so;general;/home/kde-devel/kde-qt/lib/libQtXml.so;general;/home/kde-devel/kde-qt/lib/libQtDBus.so;

//Value Computed by CMake
sopranoindex_BINARY_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/build/index

//Dependencies for the target
sopranoindex_LIB_DEPENDS:STATIC=general;/home/kde-devel/kde-qt/lib/libQtCore.so;general;-lpthread;general;soprano;general;/usr/lib/libclucene.so;

//Value Computed by CMake
sopranoindex_SOURCE_DIR:STATIC=/home/kde-devel/Download/soprano-2.3.1/index

//Dependencies for the target
sopranoserver_LIB_DEPENDS:STATIC=general;soprano;general;/home/kde-devel/kde-qt/lib/libQtCore.so;general;-lpthread;general;/home/kde-devel/kde-qt/lib/libQtNetwork.so;general;/home/kde-devel/kde-qt/lib/libQtDBus.so;


########################
# INTERNAL cache entries
########################

//Advanced flag for variable: CLUCENE_INCLUDE_DIR
CLUCENE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: CLUCENE_LIBRARY
CLUCENE_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: CLUCENE_LIBRARY_DIR
CLUCENE_LIBRARY_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1
//What is the target build tool cmake is generating for.
CMAKE_BUILD_TOOL:INTERNAL=/usr/bin/gmake
//This is the directory where this CMakeCahe.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/home/kde-devel/Download/soprano-2.3.1/build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=2
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=6
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_RELEASE_VERSION:INTERNAL=patch 2
//Advanced flag for variable: CMAKE_COLOR_MAKEFILE
CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
//Advanced flag for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
CMAKE_CXX_COMPILER_WORKS:INTERNAL=1
//Advanced flag for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
CMAKE_C_COMPILER_WORKS:INTERNAL=1
//Advanced flag for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_DETERMINE_CXX_ABI_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
CMAKE_DETERMINE_C_ABI_COMPILED:INTERNAL=TRUE
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=/usr/bin/ccmake
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Have function connect
CMAKE_HAVE_CONNECT:INTERNAL=1
//Have function gethostbyname
CMAKE_HAVE_GETHOSTBYNAME:INTERNAL=1
//Have library pthreads
CMAKE_HAVE_PTHREADS_CREATE:INTERNAL=
//Have library pthread
CMAKE_HAVE_PTHREAD_CREATE:INTERNAL=1
//Have include CMAKE_HAVE_PTHREAD_H
CMAKE_HAVE_PTHREAD_H:INTERNAL=1
//Have function remove
CMAKE_HAVE_REMOVE:INTERNAL=1
//Have function shmat
CMAKE_HAVE_SHMAT:INTERNAL=1
//Start directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/home/kde-devel/Download/soprano-2.3.1
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0
//Have library ICE
CMAKE_LIB_ICE_HAS_ICECONNECTIONNUMBER:INTERNAL=1
//Advanced flag for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=28
//Advanced flag for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/usr/share/cmake
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//Advanced flag for variable: CMAKE_USE_RELATIVE_PATHS
CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_DEB
CPACK_BINARY_DEB-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_NSIS
CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_RPM
CPACK_BINARY_RPM-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_STGZ
CPACK_BINARY_STGZ-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_TBZ2
CPACK_BINARY_TBZ2-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_TGZ
CPACK_BINARY_TGZ-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_BINARY_TZ
CPACK_BINARY_TZ-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_SOURCE_TBZ2
CPACK_SOURCE_TBZ2-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_SOURCE_TGZ
CPACK_SOURCE_TGZ-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_SOURCE_TZ
CPACK_SOURCE_TZ-ADVANCED:INTERNAL=1
//Advanced flag for variable: CPACK_SOURCE_ZIP
CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE]
//Details about finding X11
FIND_PACKAGE_MESSAGE_DETAILS_X11:INTERNAL=[/usr/lib/libX11.so][/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include]
//Have function raptor_new_iostream_from_handler2
HAVE_IOSTREAM_HANDLER2:INTERNAL=1
//Advanced flag for variable: JAVA_AWT_INCLUDE_PATH
JAVA_AWT_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: JAVA_AWT_LIBRARY
JAVA_AWT_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: JAVA_INCLUDE_PATH
JAVA_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: JAVA_INCLUDE_PATH2
JAVA_INCLUDE_PATH2-ADVANCED:INTERNAL=1
//Advanced flag for variable: JAVA_JVM_LIBRARY
JAVA_JVM_LIBRARY-ADVANCED:INTERNAL=1
QT_BINARY_DIR:INTERNAL=/home/kde-devel/kde-qt/bin
//Advanced flag for variable: QT_DBUSCPP2XML_EXECUTABLE
QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_DBUSXML2CPP_EXECUTABLE
QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_DOC_DIR
QT_DOC_DIR-ADVANCED:INTERNAL=1
QT_HEADERS_DIR:INTERNAL=/home/kde-devel/kde-qt/include
//Advanced flag for variable: QT_INCLUDE_DIR
QT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_LIBRARY_DIR
QT_LIBRARY_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_MKSPECS_DIR
QT_MKSPECS_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_MOC_EXECUTABLE
QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_PLUGINS_DIR
QT_PLUGINS_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QT3SUPPORT_INCLUDE_DIR
QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QT3SUPPORT_LIBRARY
QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTASSISTANT_INCLUDE_DIR
QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTASSISTANT_LIBRARY
QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTCORE_INCLUDE_DIR
QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTCORE_LIBRARY
QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDBUS_INCLUDE_DIR
QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDBUS_LIBRARY
QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY
QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDESIGNER_INCLUDE_DIR
QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTDESIGNER_LIBRARY
QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTGUI_INCLUDE_DIR
QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTGUI_LIBRARY
QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTMOTIF_INCLUDE_DIR
QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTMOTIF_LIBRARY
QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTNETWORK_INCLUDE_DIR
QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTNETWORK_LIBRARY
QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTNSPLUGIN_INCLUDE_DIR
QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTNSPLUGIN_LIBRARY
QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTOPENGL_INCLUDE_DIR
QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTOPENGL_LIBRARY
QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSCRIPT_INCLUDE_DIR
QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSCRIPT_LIBRARY
QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSQL_INCLUDE_DIR
QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSQL_LIBRARY
QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSVG_INCLUDE_DIR
QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTSVG_LIBRARY
QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTTEST_INCLUDE_DIR
QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTTEST_LIBRARY
QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTUITOOLS_INCLUDE_DIR
QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTUITOOLS_LIBRARY
QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTXML_INCLUDE_DIR
QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QTXML_LIBRARY
QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_QT_INCLUDE_DIR
QT_QT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_RCC_EXECUTABLE
QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_UIC3_EXECUTABLE
QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1
//Advanced flag for variable: QT_UIC_EXECUTABLE
QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1
//Have symbol Q_WS_MAC
Q_WS_MAC:INTERNAL=
//Have symbol Q_WS_QWS
Q_WS_QWS:INTERNAL=
//Have symbol Q_WS_WIN
Q_WS_WIN:INTERNAL=
//Have symbol Q_WS_X11
Q_WS_X11:INTERNAL=1
//Advanced flag for variable: RAPTOR_INCLUDE_DIR
RAPTOR_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: RAPTOR_LIBRARIES
RAPTOR_LIBRARIES-ADVANCED:INTERNAL=1
//Advanced flag for variable: RASQAL_INCLUDE_DIR
RASQAL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: RASQAL_LIBRARIES
RASQAL_LIBRARIES-ADVANCED:INTERNAL=1
//Advanced flag for variable: REDLAND_INCLUDE_DIR
REDLAND_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Advanced flag for variable: REDLAND_LIBRARIES
REDLAND_LIBRARIES-ADVANCED:INTERNAL=1
//Soprano Index is built
SOPRANO_BUILD_INDEX_LIB:INTERNAL=1
//Advanced flag for variable: X11_ICE_INCLUDE_PATH
X11_ICE_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_ICE_LIB
X11_ICE_LIB-ADVANCED:INTERNAL=1
//Have library /usr/lib/libX11.so;/usr/lib/libXext.so
X11_LIB_X11_SOLO:INTERNAL=1
//Advanced flag for variable: X11_SM_LIB
X11_SM_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_X11_INCLUDE_PATH
X11_X11_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_X11_LIB
X11_X11_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_XShm_INCLUDE_PATH
X11_XShm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_XTest_INCLUDE_PATH
X11_XTest_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_XTest_LIB
X11_XTest_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xaccessrules_INCLUDE_PATH
X11_Xaccessrules_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xaccessstr_INCLUDE_PATH
X11_Xaccessstr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xau_INCLUDE_PATH
X11_Xau_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xau_LIB
X11_Xau_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xcomposite_INCLUDE_PATH
X11_Xcomposite_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xcomposite_LIB
X11_Xcomposite_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xcursor_INCLUDE_PATH
X11_Xcursor_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xcursor_LIB
X11_Xcursor_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xdamage_INCLUDE_PATH
X11_Xdamage_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xdamage_LIB
X11_Xdamage_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xdmcp_INCLUDE_PATH
X11_Xdmcp_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xdmcp_LIB
X11_Xdmcp_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xext_LIB
X11_Xext_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xfixes_INCLUDE_PATH
X11_Xfixes_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xfixes_LIB
X11_Xfixes_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xft_INCLUDE_PATH
X11_Xft_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xft_LIB
X11_Xft_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xinerama_INCLUDE_PATH
X11_Xinerama_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xinerama_LIB
X11_Xinerama_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xinput_INCLUDE_PATH
X11_Xinput_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xinput_LIB
X11_Xinput_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xkb_INCLUDE_PATH
X11_Xkb_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xkblib_INCLUDE_PATH
X11_Xkblib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xlib_INCLUDE_PATH
X11_Xlib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xpm_INCLUDE_PATH
X11_Xpm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xpm_LIB
X11_Xpm_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xrandr_INCLUDE_PATH
X11_Xrandr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xrandr_LIB
X11_Xrandr_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xrender_INCLUDE_PATH
X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xrender_LIB
X11_Xrender_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xscreensaver_INCLUDE_PATH
X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xscreensaver_LIB
X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xshape_INCLUDE_PATH
X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xt_INCLUDE_PATH
X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xt_LIB
X11_Xt_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xutil_INCLUDE_PATH
X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xv_INCLUDE_PATH
X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xv_LIB
X11_Xv_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_Xxf86misc_LIB
X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_dpms_INCLUDE_PATH
X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_xf86misc_INCLUDE_PATH
X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Advanced flag for variable: X11_xf86vmode_INCLUDE_PATH
X11_xf86vmode_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Test __SOPRANO_HAVE_GCC_VISIBILITY
__SOPRANO_HAVE_GCC_VISIBILITY:INTERNAL=1


project(soprano)

cmake_minimum_required(VERSION 2.6.2)

set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${CMAKE_CURRENT_SOURCE_DIR}/cmake/modules)

##################  Soprano version  ################################
set(CMAKE_SOPRANO_VERSION_MAJOR 2)
set(CMAKE_SOPRANO_VERSION_MINOR 3)
set(CMAKE_SOPRANO_VERSION_RELEASE 1)
set(CMAKE_SOPRANO_VERSION_STRING "${CMAKE_SOPRANO_VERSION_MAJOR}.${CMAKE_SOPRANO_VERSION_MINOR}.${CMAKE_SOPRANO_VERSION_RELEASE}")


##################  User options  ################################

option(SOPRANO_BUILD_TESTS "Build all unit tests")
option(SOPRANO_DISABLE_REDLAND_BACKEND "Disable the compilation of the redland backend")
option(SOPRANO_DISABLE_SESAME2_BACKEND "Disable the compilation of the sesame2 backend")
option(SOPRANO_DISABLE_CLUCENE_INDEX "Disable the compilation of the clucene-based full-text index")
option(SOPRANO_DISABLE_RAPTOR_PARSER "Disable the compilation of the raptor parser and serializer plugins (provides most Soprano parsers and serializers)")
option(SOPRANO_DISABLE_DBUS "Disable the D-Bus integration")
option(SOPRANO_BUILD_API_DOCS "Build the Soprano API documentation")

if(SOPRANO_BUILD_TESTS)
  enable_testing()
endif(SOPRANO_BUILD_TESTS)

if(WIN32)
  set(CMAKE_DEBUG_POSTFIX "d")
endif(WIN32)

include(SopranoCPack.cmake)

##################  find packages  ################################

set(QT_MIN_VERSION "4.4.0")
find_package(Qt4 REQUIRED)
# properly set up compile flags (QT_DEBUG/QT_NO_DEBUG, ...)
include(${QT_USE_FILE})

if(NOT SOPRANO_DISABLE_RAPTOR_PARSER OR NOT SOPRANO_DISABLE_REDLAND_BACKEND)
  find_package(Rasqal)
  find_package(Raptor)
  find_package(Redland)

  if(WIN32)
    if(NOT REDLAND_VERSION)
      set(REDLAND_VERSION "1.0.3")
      message(STATUS "Windows currently only has Redland version 1.0.3")
    endif(NOT REDLAND_VERSION)
  endif(WIN32)
endif(NOT SOPRANO_DISABLE_RAPTOR_PARSER OR NOT SOPRANO_DISABLE_REDLAND_BACKEND)

if(NOT SOPRANO_DISABLE_CLUCENE_INDEX)
  find_package(CLucene)
  if(CLucene_FOUND)
    if(CLUCENE_VERSION AND CLUCENE_VERSION STRGREATER "0.9.19" OR CLUCENE_VERSION STREQUAL "0.9.19")
      set(CL_VERSION_19_OR_GREATER TRUE)
    endif(CLUCENE_VERSION AND CLUCENE_VERSION STRGREATER "0.9.19" OR CLUCENE_VERSION STREQUAL "0.9.19")
    set(SOPRANO_BUILD_INDEX_LIB 1 CACHE INTERNAL "Soprano Index is built" FORCE)
  endif(CLucene_FOUND)
endif(NOT SOPRANO_DISABLE_CLUCENE_INDEX)

if(NOT SOPRANO_DISABLE_SESAME2_BACKEND)
  find_package(JNI)
  if(JAVA_INCLUDE_PATH AND JAVA_JVM_LIBRARY)
    file(READ ${JAVA_INCLUDE_PATH}/jni.h jni_header_data)
    string(REGEX MATCH "JNI_VERSION_1_4" JNI_1_4_FOUND "${jni_header_data}")
    if(JNI_1_4_FOUND)
      message(STATUS "Found Java JNI >= 1.4: ${JAVA_INCLUDE_PATH}, ${JAVA_JVM_LIBRARY}")
    else(JNI_1_4_FOUND)
      message( "Need JNI version 1.4 or higher for the Sesame2 backend.")
    endif(JNI_1_4_FOUND)
  else(JAVA_INCLUDE_PATH AND JAVA_JVM_LIBRARY)
    message(STATUS "Could not find Java JNI")
    if("$ENV{JAVA_HOME}" STREQUAL "")
      message("Make sure JAVA_HOME is set")
    endif("$ENV{JAVA_HOME}" STREQUAL "")
  endif(JAVA_INCLUDE_PATH AND JAVA_JVM_LIBRARY)
endif(NOT SOPRANO_DISABLE_SESAME2_BACKEND)


##################  setup variables  ################################
if(REDLAND_FOUND AND NOT SOPRANO_DISABLE_REDLAND_BACKEND)
  set(BUILD_REDLAND_BACKEND TRUE)
endif(REDLAND_FOUND AND NOT SOPRANO_DISABLE_REDLAND_BACKEND)
if(JNI_1_4_FOUND AND NOT SOPRANO_DISABLE_SESAME2_BACKEND)
  set(BUILD_SESAME2_BACKEND TRUE)
endif(JNI_1_4_FOUND AND NOT SOPRANO_DISABLE_SESAME2_BACKEND)
if(SOPRANO_BUILD_INDEX_LIB AND NOT SOPRANO_DISABLE_CLUCENE_INDEX)
  set(BUILD_CLUCENE_INDEX TRUE)
endif(SOPRANO_BUILD_INDEX_LIB AND NOT SOPRANO_DISABLE_CLUCENE_INDEX)
if(RAPTOR_FOUND AND NOT SOPRANO_DISABLE_RAPTOR_PARSER)
  set(BUILD_RAPTOR_PARSER TRUE)
endif(RAPTOR_FOUND AND NOT SOPRANO_DISABLE_RAPTOR_PARSER)
if(RAPTOR_FOUND AND REDLAND_FOUND AND REDLAND_VERSION STRGREATER "1.0.5" AND NOT SOPRANO_DISABLE_RAPTOR_PARSER)
  set(BUILD_RAPTOR_SERIALIZER TRUE)
endif(RAPTOR_FOUND AND REDLAND_FOUND AND REDLAND_VERSION STRGREATER "1.0.5" AND NOT SOPRANO_DISABLE_RAPTOR_PARSER)
if(NOT SOPRANO_DISABLE_DBUS AND QT_QTDBUS_FOUND)
  set(BUILD_DBUS_SUPPORT TRUE)
endif(NOT SOPRANO_DISABLE_DBUS AND QT_QTDBUS_FOUND)
set(HAVE_DBUS BUILD_DBUS_SUPPORT)

##################  setup install directories  ################################
set (LIB_SUFFIX "" CACHE STRING "Define suffix of directory name (32/64)" )
set (LIB_DESTINATION "${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}" CACHE STRING "Library directory name")
## the following are directories where stuff will be installed to
set(INCLUDE_INSTALL_DIR      "${CMAKE_INSTALL_PREFIX}/include/" CACHE PATH "The subdirectory to the header prefix")
set(PKGCONFIG_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}/pkgconfig/" CACHE STRING "Base directory for pkgconfig files")


# Set up RPATH handling, so the libs are found if they are installed to a non-standard location.
# By default cmake builds the targets with full RPATH to everything in the build directory,
# but then removes the RPATH when installing.
# These two options below make it set the RPATH of the installed targets to all
# RPATH directories outside the current CMAKE_BINARY_DIR and also the library
# install directory. Alex
set(CMAKE_INSTALL_RPATH_USE_LINK_PATH  TRUE)
set(CMAKE_INSTALL_RPATH                ${LIB_DESTINATION} )

if(APPLE)
   set(CMAKE_INSTALL_NAME_DIR ${LIB_DESTINATION})
endif(APPLE)


##################  some compiler settings ################################
if(CMAKE_COMPILER_IS_GNUCXX AND NOT WIN32 )
    set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-check-new -fno-common")
endif(CMAKE_COMPILER_IS_GNUCXX AND NOT WIN32 )
if(MSVC)
    add_definitions(-D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -Zc:wchar_t-)
endif(MSVC)
if(MINGW)
    set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -Wpointer-arith -Wformat-security -fno-check-new -fno-common")
endif(MINGW)


##################  add subdirectories ################################
if(BUILD_CLUCENE_INDEX)
   add_subdirectory(index)
endif(BUILD_CLUCENE_INDEX)
add_subdirectory(soprano)
add_subdirectory(backends)
add_subdirectory(parsers)
add_subdirectory(serializers)
add_subdirectory(server)
add_subdirectory(tools)
add_subdirectory(rules)
add_subdirectory(includes)
if(SOPRANO_BUILD_TESTS)
  add_subdirectory(test)
endif(SOPRANO_BUILD_TESTS)
add_subdirectory(cmake)


##################  create pkgconfig file  ################################
if(NOT WIN32)
  configure_file(${CMAKE_CURRENT_SOURCE_DIR}/soprano.pc.cmake ${CMAKE_CURRENT_BINARY_DIR}/soprano.pc @ONLY)
  install(FILES ${CMAKE_CURRENT_BINARY_DIR}/soprano.pc DESTINATION ${PKGCONFIG_INSTALL_PREFIX})
endif(NOT WIN32)


##################  apidox ################################
if(SOPRANO_BUILD_API_DOCS)
  find_package(Doxygen)

  if(DOXYGEN_EXECUTABLE)
    configure_file(${soprano_SOURCE_DIR}/Doxyfile.cmake ${soprano_BINARY_DIR}/Doxyfile)

    if(EXISTS ${QT_DOC_DIR}/html)
      set(QTDOCS "${QT_DOC_DIR}/html")
    else(EXISTS ${QT_DOC_DIR}/html)
      set(QTDOCS "http://doc.trolltech.com/4.3/")
    endif(EXISTS ${QT_DOC_DIR}/html)

    add_custom_target(
      apidox ALL
      COMMAND ${DOXYGEN_EXECUTABLE} Doxyfile
      COMMAND docs/html/installdox -l qt4.tag@${QTDOCS} docs/html/*.html)
  endif(DOXYGEN_EXECUTABLE)
endif(SOPRANO_BUILD_API_DOCS)


##################  status messages ################################
message("---------------------------------------------------------------------------------------")
message("-- Soprano Components that will be built:")
if(NOT BUILD_REDLAND_BACKEND AND NOT BUILD_SESAME2_BACKEND)
  message("   WARNING: No Soprano backends will be compiled!")
  message("   WARNING: Soprano will not be very useful without storage backends!")
endif(NOT BUILD_REDLAND_BACKEND AND NOT BUILD_SESAME2_BACKEND)
if(BUILD_REDLAND_BACKEND)
  message("   * Redland storage backend")
endif(BUILD_REDLAND_BACKEND)
if(BUILD_SESAME2_BACKEND)
  message("   * Sesame2 storage backend (java-based)")
endif(BUILD_SESAME2_BACKEND)

if(BUILD_RAPTOR_PARSER)
  message("   * Raptor RDF parser")
  if(RAPTOR_HAVE_TRIG)
    message("     (including TriG parser)")
  endif(RAPTOR_HAVE_TRIG)
endif(BUILD_RAPTOR_PARSER)

if(BUILD_RAPTOR_SERIALIZER)
  message("   * Raptor RDF serializer")
endif(BUILD_RAPTOR_SERIALIZER)

if(BUILD_CLUCENE_INDEX)
  message("   * The CLucene-based full-text search index library")
endif(BUILD_CLUCENE_INDEX)

if(BUILD_DBUS_SUPPORT)
  message("   * D-Bus server/client support")
endif(BUILD_DBUS_SUPPORT)


message("")
message("-- Soprano Components that will NOT be built:")
if(NOT BUILD_REDLAND_BACKEND)
  message("   * Redland storage backend")
endif(NOT BUILD_REDLAND_BACKEND)
if(NOT BUILD_SESAME2_BACKEND)
  message("   * Sesame2 storage backend (java-based)")
endif(NOT BUILD_SESAME2_BACKEND)

if(NOT BUILD_RAPTOR_PARSER)
  message("   * Raptor RDF parser")
endif(NOT BUILD_RAPTOR_PARSER)

if(NOT BUILD_RAPTOR_SERIALIZER)
  message("   * Raptor RDF serializer")
  if(NOT SOPRANO_DISABLE_RAPTOR_PARSER AND REDLAND_FOUND AND REDLAND_VERSION STRLESS "1.0.6")
    message("     (The Raptor serializer depends on Redland 1.0.6 or greater.")
  endif(NOT SOPRANO_DISABLE_RAPTOR_PARSER AND REDLAND_FOUND AND REDLAND_VERSION STRLESS "1.0.6")
endif(NOT BUILD_RAPTOR_SERIALIZER)

if(NOT BUILD_CLUCENE_INDEX)
  message("   * The CLucene-based full-text search index library")
endif(NOT BUILD_CLUCENE_INDEX)

if(NOT BUILD_DBUS_SUPPORT)
  message("   * D-Bus server/client support")
endif(NOT BUILD_DBUS_SUPPORT)

message("---------------------------------------------------------------------------------------")

Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to trig

by Sebastian Trueg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Please state the actual problem again as the email history does not seem to
contain it...

On Monday 09 November 2009 23:16:21 Abhinav Chaturvedi wrote:

> Hi Sebastian,
> I tried what you suggested. And this is what I got:
>
> redland-config --version = 1.0.8
> raptor-config --version = 1.4.18
> rasqal-config --version = 0.9.16
>
> Attached are 2 files:
> 1. CMakeCache.txt file in the build folder one needs to create before
> compiling Soprano
> 2. CMakeLists.txt file from ../build
>
> I see options like SOPRANO_DISABLE_RAPTOR_PARSER:BOOL=OFF in
> the CMakeCache.txt file. So I am thinking that everything that is needed
> should have been compiled from scratch. Did I miss something when doing
> 'cmake'?
>
> Thanks
> Abhinav.
>
>
> 2009/11/10 <kde-core-devel-request@...>
>
> > Send kde-core-devel mailing list submissions to
> >        kde-core-devel@...
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >        https://mail.kde.org/mailman/listinfo/kde-core-devel
> > or, via email, send a message with subject or body 'help' to
> >        kde-core-devel-request@...
> >
> > You can reach the person managing the list at
> >        kde-core-devel-owner@...
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of kde-core-devel digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Re: Review Request: startup faster;       don't wait for kwin or
> >      kcm's in ksmserver (Lubos Lunak)
> >   2. Re: chess and barcelona (Marco Martin)
> >   3. Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to
> >      trig (Sebastian Trueg)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 9 Nov 2009 14:56:33 +0100
> > From: Lubos Lunak <l.lunak@...>
> > Subject: Re: Review Request: startup faster;    don't wait for kwin or
> >        kcm's in ksmserver
> > To: kde-core-devel@...
> > Message-ID: <200911091456.33717.l.lunak@...>
> > Content-Type: text/plain;  charset="utf-8"
> >
> > On Saturday 07 of November 2009, Sebastian Sauer wrote:
> > > > On 2009-11-04 10:10:06, Lubos Lunak wrote:
> > > > > The reason for waiting for the WM to finish setup is not the
> >
> > fallback,
> >
> > > > > but making sure the WM is ready. There are some aspects related to
> > > > > window management where applications just read the status during
> >
> > their
> >
> > > > > startup and don't update later. So waiting for the WM ensures this
> > > > > is set up properly before other applications may read that
> > > > > (although, thinking of that, this is currently a bit broken anyway,
> > > > > as KWin lets ksmserver continue a bit too soon).
> > > > >
> > > > > The second case is something similar. The kcminit modules do
> > > > > various setup and it is a question if it is ok to let normal apps
> > > > > start while this is still taking place.
> > >
> > > Specs are relative. Cold start (not initial) takes up to 9 seconds till
> >
> > the
> >
> > > plasma desktop is visible / ksplashx closes.
> >
> >  Hmm. Twice 1/2s is not that insignificant then :-/.
> >
> > > The thing is that the wm starts very early. Even before plasma which
> > > does not need the wm at this point. The first "real" applications are
> > > rather late started/restored. Maybe we should just wait in
> > > KSMServer::autoStart1Done() till the wm is ready? Would that be enough?
> >
> >  Plasma is not different from other applications in this regard, in fact,
> > it
> > may depend more on it - compositing status, number of virtual desktops,
> > etc.
> > I have no idea what would happen if e.g. Plasma thought there was just 1
> > virtual desktop because it saw that too soon.
> >
> > > The kde startup process has lot of potential for optimizations.
> >
> >  It is intentionally designed that way. The original application
> > launching code (around KSMServer::tryRestoreNext()) is written to launch
> > apps one by one. IIRC the reason for that was that computers[*] of those
> > days were bad at
> > handling the load and putting sleeps here and there actually improved the
> > overall situation. I doubt anyone has benchmarked this in a reasonably
> > recent
> > time.
> >
> > [*] Or maybe we could blame the kernel.
> >
> > > Time
> > > expensive things like e.g. kcminit are atm blocking the whole startup.
> >
> > Long
> >
> > > term we need to have expensive things run in parallel at startup.
> > > Anyway, if you think that this is not a good idea then it should be
> > > maybe done another way.
> >
> >  I don't know if there is another way. The code can be changed to launch
> > normal apps in parallel if that helps, there would be no problem with
> > that. But the rest currently has certain ordering (see ksmserver/README)
> > with some
> > implications. For example startup phase 0 (i.e. Plasma) is done quite
> > early and waited for completion in order to have the desktop ready, hide
> > the splash
> > and give the impression that the desktop or more or less ready while
> > normal apps are still being loaded. Moving things one way can mean the
> > splash is shown needlessly long when the desktop could be already usable,
> > opposite way
> > would be showing desktop that is still not usable (as is the case with
> > some Windows versions and AFAIK it's rather annoying).
> >
> >  If you would have some time to spend on this, it would be interesting if
> > you
> > could analyze the KDE startup as a whole and see where the time is spent
> > (note: cold vs warm disk caches did tripple the number when I tested that
> > the
> > last time, so pay attention to that). With that thinking about doing some
> > rearranging should be simpler.
> >
> > --
> > Lubos Lunak
> > KDE developer
> > --------------------------------------------------------------
> > SUSE LINUX, s.r.o.   e-mail: l.lunak@... , l.lunak@...
> > Lihovarska 1060/12   tel: +420 284 084 672
> > 190 00 Prague 9      fax: +420 284 028 951
> > Czech Republic       http://www.suse.cz
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Mon, 9 Nov 2009 17:22:02 +0100
> > From: Marco Martin <notmart@...>
> > Subject: Re: chess and barcelona
> > To: kde-core-devel@...
> > Message-ID: <200911091722.02201.notmart@...>
> > Content-Type: Text/Plain;  charset="iso-8859-1"
> >
> > On Sunday 08 November 2009, Albert Astals Cid wrote:
> > > A Diumenge, 8 de novembre de 2009, Inge Wallin va escriure:
> > > > On Sunday 08 November 2009 20:56:20 Albert Astals Cid wrote:
> > > > > A Diumenge, 8 de novembre de 2009, Frank Karlitschek va escriure:
> > > > > > Hi,
> > > > > >
> > > > > > as a favor for Quim Gil from Maemo I forward two things to you
> >
> > which
> >
> > > > > > might be interesting.
> > > > > >
> > > > > >
> > > > > > 1. The Maemo people are doing a "UX meets Code" Hackfest in
> >
> > Barcelona
> >
> > > > > > in December.
> > > > > > All KDE people are invited. Please see this page if you are
> > > > > > interested to participate.
> > > > > > http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend
> > > > > >
> > > > > >
> > > > > > 2. Quim is looking for developers to help with a Qt 4.6 based
> > > > > > chess game for Maemo.
> > > > > > Check this page if you want to help:
> > > > > > http://wiki.maemo.org/Miniature
> > > > >
> > > > > You want kde-games-devel@... for KDE games developers, but not
> >
> > sure
> >
> > > > >  people there is interested in doing Qt/Maemo development, since
> > > > > it's really not KDE development after all.
> > > >
> > > > I think this reasoning is wrong.  KDE is not just the desktop
> >
> > environment
> >
> > > >  any more, it's the toolkit, including kdelibs and the community.
> > > > Nowadays KDE applications are cross platform, and the more we can get
> > > > into the mobile devices and make our apps run on small form factors
> > > > the better.
> > > >
> > > > Development for Maemo is just our next frontier.
> > >
> > > We disagree here :-)
> > >
> > > As part of the KDE community I care the less for Maemo until it ships
> >
> > KDE,
> >
> > >  it shipping Qt is cool because means i have knowledge to code for it
> > > if
> >
> > i
> >
> > >  feel like, it gives me more job opportunities, and probably creates
> > > more
> >
> > well, the opportunity for Maemo to ship KDE should also be created, if we
> > don't push it i doubt that will happen any day, if we show that using
> > kdelibs
> > there besides Qt can have clear advantage could instead make it happen,
> > and being on a potentially successful smartphone platform is indeed
> > -very- interesting
> >
> > Cheers,
> > Marco Martin
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Mon, 09 Nov 2009 19:57:12 +0100
> > From: Sebastian Trueg <trueg@...>
> > Subject: Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to
> >        trig
> > To: kde-core-devel@...
> > Message-ID: <4AF86608.6020801@...>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Abhinav Chaturvedi wrote:
> > > Hi Sebastian,
> > > I cannot seem to find which version of libredland and libraptor I have.
> > > But what I can tell you is that I downloaded Soprano-2.3.1 and compiled
> > > it into /usr/local.
> >
> > redland-config --version
> > should help here.
> >
> > > It is this Soprano that I then used during kdebase compilation. I was
> > > compiling KDE-4.3.3 on an OpenSuse-11.1 system (which has KDE-4.1.x).
> > > For now, I have managed to compile kdebase by disabling Nepomuk
> > > compilation (BUILD_nepomuk:BOOL=OFF in CMakeCache.txt).
> >
> > Could you get the cmake output from your own Soprano compilation to me?
> >
> > > I don't know whether there is any connection between Soprano and
> > > Nepomuk. So, i don't know whether you can infer redland and raptor
> > > versions from the Soprano version number.
> >
> > Nepomuk is based on Soprano.
> >
> > > But if you could tell me of a way to find the redland and raptor
> > > versions, then I'll hurry the answers back to you.
> > >
> > > Thanks for your help
> > > Abhinav.
> > >
> > > 2009/11/5 <kde-core-devel-request@...
> > > <mailto:kde-core-devel-request@...>>
> > >
> > >     Send kde-core-devel mailing list submissions to
> > >            kde-core-devel@... <mailto:kde-core-devel@...>
> > >
> > >     To subscribe or unsubscribe via the World Wide Web, visit
> > >            https://mail.kde.org/mailman/listinfo/kde-core-devel
> > >     or, via email, send a message with subject or body 'help' to
> > >            kde-core-devel-request@...
> > >     <mailto:kde-core-devel-request@...>
> > >
> > >     You can reach the person managing the list at
> > >            kde-core-devel-owner@...
> > >     <mailto:kde-core-devel-owner@...>
> > >
> > >     When replying, please edit your Subject line so it is more specific
> > >     than "Re: Contents of kde-core-devel digest..."
> > >
> > >
> > >     Today's Topics:
> > >
> > >       1. Re: Qt KDE integration in kdereview. (Diego Iastrubni)
> > >       2. Re: Attica moved to kdereview (Frederik Gladhorn)
> > >       3. Re: device-automounter moved to kdereview (Albert Astals Cid)
> > >       4. Re: Bugreporting barrier is too low with the new Dr. Konqi
> > >          (Dar?o Andr?s)
> > >       5. Re: [newbie]: Problems compiling kdebase-4.3 due to trig
> > >          (Sebastian Tr?g)
> > >       6. Re: Qt KDE integration in kdereview. (Olivier Goffart)
> > >       7. Re: KDE is not an OS platform... (And neither is Gnome)
> > >          (Alexander Neundorf)
> > >       8. Re: Qt KDE integration in kdereview. (Alexander Neundorf)
> > >       9. Re: Rocs moved to kdereview. (Tomaz Canabrava)
> >
> > ----------------------------------------------------------------------
> >
> > >     Message: 1
> > >     Date: Wed, 4 Nov 2009 21:07:11 +0200
> > >     From: Diego Iastrubni <elcuco@... <mailto:elcuco@...>>
> > >     Subject: Re: Qt KDE integration in kdereview.
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042107.11986.elcuco@...
> > >     <mailto:200911042107.11986.elcuco@...>>
> > >     Content-Type: Text/Plain;  charset="iso-8859-1"
> > >
> > >     On Tuesday 03 November 2009 21:11:21 David Faure wrote:
> > >     > On Tuesday 03 November 2009, Diego Iastrubni wrote:
> > >     > > On Tuesday 03 November 2009 17:55:51 Olivier Goffart wrote:
> > >     > > > Hello.
> > >     > > >
> > >     > > > I have just submitted a new plugin in kdereview:
> > >     > > > qguiplatformplugin_kde
> > >     > > >
> > >     > > > The objective of this plugin is to allow pure Qt Application
> > >
> > >     (not KDE
> > >
> > >     > > > ones) to get better integration into KDE.
> > >     > >
> > >     > > How about integrating KDE widgets directly into pure Qt
> > >
> > >     applications?
> > >
> > >     > > I see that QMainWindow::menuBar(), QMainWindow::statusBar() and
> > >     > > QMainWindow::addToolBar(QString) can be hacked. Maybe that
> > >
> > >     plugin can
> > >
> > >     > >  provide the menu/statusbar/toolbar "virtual constructors" or
> > >
> > >     something.
> > >
> > >     > You mean in order to create KMainWindows and KToolBars?
> > >     > What would this provide to the Qt applications?
> > >
> > >     making a KMainWindow, from a QMainWindow should be difficult.
> > >     However, one of
> > >     the most missing features for me in QToolBars are the icon/text
> > >     settings and
> > >     the lock toolbars command.
> > >
> > >     I am just thinking aloud: how hard can this be?
> > >
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 2
> > >     Date: Wed, 04 Nov 2009 20:12:06 +0100
> > >     From: Frederik Gladhorn <gladhorn@...
> > > <mailto:gladhorn@...>> Subject: Re: Attica moved to kdereview
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <4af1d3da.0f1abc0a.68f4.3f25@...
> > >     <mailto:4af1d3da.0f1abc0a.68f4.3f25@...>>
> > >     Content-Type: text/plain; charset="ISO-8859-1"
> > >
> > >     Hola Albert,
> > >     thanks a lot for the review!
> > >     I hope that we addressed your points by now.
> > >
> > >     Albert Astals Cid wrote:
> > >     > A Dimarts, 3 de novembre de 2009, Frederik Gladhorn va escriure:
> > >     >> Hi all,
> > >     >> after spending some time with libattica, we decided that now is
> > >     >> a
> > >
> > >     good
> > >
> > >     >>  point to get a review for it and eventually have it used in
> > >     >> KDE.
> > >     >
> > >     > The licensing is unclear, activity.h is GPL2+ while
> > >     > downloaditem.h
> >
> > is
> >
> > >     > LGPL2+
> > >
> > >     Done, we forgot to make it the same everywhere, it's relicensed to
> > >     LGPL2+ in
> > >     agreement with all authors now.
> > >
> > >     > You have one foreach without const & in the "iterator"
> > >
> > >     /me hides :D
> > >
> > >     > Maybe it would make sense to d-pointify Attica:BaseJob::Metadata,
> > >     > Attica::DownloadUrlDescription, Attica::GetJob, Attica::PostJob
> > >
> > >     Mostly done, will be finished tomorrow.
> > >
> > >     > In Attica::DownloadUrlDescription if you put the two bools
> > >
> > >     together your
> > >
> > >     > struct will use less memory
> > >
> > >     Done.
> > >
> > >     > Should downloadUrlDescription(), previewPicture(), license(),
> > >
> > >     author() of
> > >
> > >     > Attica::Content be const?
> > >
> > >     Done.
> > >
> > >     > Should url() in Attica::DownloadItem be const?
> > >
> > >     Yes.
> > >
> > >     > Any reason to make Attica::DownloadItem use a
> > >     > QExplicitlySharedDataPointer?
> > >
> > >     Total nonsense and an oversight by me.
> > >     Seems like I wasn't quite awake when writing that class...
> > >
> > >     > From the application point of view, it would make sense to me
> > >     > that
> > >
> > >     if for
> > >
> > >     > example it makes no sense that the application ever calls
> > >     > Folder::setMessageCount it should be private and called by a
> > >
> > >     friend class.
> > >
> > >     > But maybe it makes sense calling Folder::setMessageCount and it's
> > >
> > >     ok :D
> > >     Since we support creating items and sending them to the server
> > >     again, most
> > >     setters make sense. The case you asked about is indeed
> > > questionable.
> > >
> > >     > After a quick look at the API i'm not sure if the Jobs are
> > >
> > >     supposed to be
> > >
> > >     > part of the public API or not. Their headers are installed an the
> > >
> > >     classes
> > >
> > >     > exported, but
> > >     >
> > >     > GetJob(const QSharedPointer<Internals>& internals, const
> > >
> > >     QNetworkRequest&
> > >
> > >     > request);
> > >     > seems a bit weird, what's that QSharedPointer<Internals>?
> > >
> > >     Yep, this is supposed to be used only internally. You just get
> > >     instances of
> > >     these classes back from Attica::Provider. Constructors changed to
> > >     private or
> > >     protected now.
> > >
> > >     Thanks!
> > >
> > >     Greetings
> > >     Frederik
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 3
> > >     Date: Wed, 4 Nov 2009 20:41:56 +0100
> > >     From: Albert Astals Cid <aacid@... <mailto:aacid@...>>
> > >     Subject: Re: device-automounter moved to kdereview
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042041.56630.aacid@...
> > >     <mailto:200911042041.56630.aacid@...>>
> > >     Content-Type: Text/Plain;  charset="iso-8859-15"
> > >
> > >     A Dimecres, 4 de novembre de 2009, Trever Fischer va escriure:
> > >     > On Tuesday 03 November 2009 6:18:43 pm Albert Astals Cid wrote:
> > >     > > A Dimarts, 3 de novembre de 2009, Jacopo De Simoi va escriure:
> > >     > > > On Tuesday 03 November 2009 02:15:20 Trever Fischer wrote:
> > >     > > > > On Monday 02 November 2009 6:45:18 pm Jacopo De Simoi wrote:
> > >     > > > > > On Monday 02 November 2009 23:56:14 Jacopo De Simoi wrote:
> > >     > > > > > > > So you /don't / have to use UDIs (unless you're
> > >
> > >     manually adding
> > >
> > >     > > > > > > > to the list) to use the feature.
> > >     > > > > > >
> > >     > > > > > > I believe we need to get rid of the UDIs and provide
> > >
> > >     some more
> > >
> > >     > > > > > > not just user-friendly, but "human-friendly" strings..
> > >
> > >     Having to
> > >
> > >     > > > > > > deal with them even in some cases is not really
> > >
> > >     acceptable. I'll
> > >
> > >     > > > > > > try to have a look into this to see how we can sort
> > >     > > > > > > this
> >
> > out
> >
> > >     > > > > > Just quickly playing with the solid minibrowser I have a
> >
> > few
> >
> > >     > > > > > suggestions
> > >     > > > > >
> > >     > > > > > First of all, show whichever icon solids give to the
> > >
> > >     device, it
> > >
> > >     > > > > > really really helps to figure out what we are talking
> > >
> > >     about even
> > >
> > >     > > > > > before we start reading.
> > >     > > > > >
> > >     > > > > > The volume property info.product is quite uninformative
> > >
> > >     (usually
> > >
> > >     > > > > >  Volume(ext3)), but if you jump back to the closest
> > >
> > >     relative which
> > >
> > >     > > > > > has a info.product property you will find quite
> > >
> > >     interesting things,
> > >
> > >     > > > > > such as ExpressCard, or stuff like that.
> > >     > > > > >
> > >     > > > > > Then I'd compose a string with the following field (with
> > >
> > >     parent I
> > >
> > >     > > > > > mean the closest device in the hierarchy which has the
> >
> > infos
> >
> > >     > > > > > required)
> > >     > > > > >
> > >     > > > > > parent.info.vendor parent.info.product
> > >     > > > > > volume.info.product
> > >
> > >     (size)
> > >
> > >     > > > > > Some real-life examples:
> > >     > > > > >
> > >     > > > > > Seagate FreeAgent Go Backup_HD (160 Go)
> > >     > > > > > ST325082 0A MediaHD (250 Go)
> > >     > > > > > Lexar ExpressCard ssdhome (5 Go)
> > >     > > > > > Lexar ExpressCard ssdroot (3 Go)
> > >     > > > > > SD02G Volume (ext3) (2 Go) (with SD icon)
> > >     > > > > > Kingston FCR-HS219/1 MicroSD (2 Go) (I'm cheating here...
> > >
> > >     MicroSD
> > >
> > >     > > > > > is the volume label)
> > >     > > > > >
> > >     > > > > > Still, as you can see there's room for improvement, in
> > >
> > >     particular
> > >
> > >     > > > > > the second guy was giving quite debatable information
> > >
> > >     about itself
> > >
> > >     > > > > > (however still better than
> > >     > > > > > /org/freedesktop/Hal/devices/volume_uuid_ECBF_30CC)
> > >     > > > >
> > >     > > > > Nonetheless a good idea. I added it to the GUI.
> > >     > > >
> > >     > > > Ok, now this looks much better; what about this, now, to make
> > >
> > >     it look
> > >
> > >     > > > even better;
> > >     > > >
> > >     > > > If (and only if) there exists more than one volume with the
> >
> > same
> >
> > >     > > > parent, group them with the parent; then the parent will be
> > >
> > >     shown with
> > >
> > >     > > > vendor() and product() and total size (should be available
> > >     > > > with storage.removable.media_size) and then each child
> > >     > > > (partition)
> > >
> > >     would
> > >
> > >     > > > just show description() and size This is visually better
> > >     > > > since
> >
> > it
> >
> > >     > > > removes redundant information for partitions of the same
> > >
> > >     drive. and
> > >
> > >     > > > makes it easier to browse.
> > >     > > >
> > >     > > > On the other hand, if a volume is an only child, then don't
> > >
> > >     add another
> > >
> > >     > > >  node and use the long description we talked about yesterday.
> > >     > > >
> > >     > > > Also, imho the informations should be refreshed even if it's
> > >
> > >     already
> > >
> > >     > > >  present in the .rc file whenever possible; besides; who is
> > >
> > >     responsible
> > >
> > >     > > > to fill in the devices in the .rc file? the daemon I suppose;
> > >
> > >     would it
> > >
> > >     > > > be possible to save the pretty name we have found for our
> > >
> > >     device at the
> > >
> > >     > > > daemon level? so that whenever you connect the drive, the
> > >     > > > user
> > >
> > >     would
> > >
> > >     > > > find it with its pretty name in the disconnected devices node
> > >
> > >     as well.
> > >
> > >     > > > Having it set up at the daemon level could make the kcm part
> > >
> > >     merely
> > >
> > >     > > > read it from the .rc since it will be automagically updated.
> > >     > > >
> > >     > > > Moreover, I believe that the Add device button is useless;
> > >
> > >     nobody would
> > >
> > >     > > >  really enter the udi of a device.
> > >     > >
> > >     > > I agree here, and the forget device is not of much use either
> > >     >
> > >     > The reason I put it in was I figured there needs to be some way
> > >     > to
> > >
> > >     undo the
> > >
> > >     > otherwise permanent memorization of "automount this device
> > >     > because
> > >
> > >     it has
> > >
> > >     >  been mounted before".
> > >     >
> > >     > > > Nice job!
> > >     > > > @Albert, what  do you think about the ui fixes?
> > >     > >
> > >     > > The list let's you do multiple selection, i don't think that
> > >
> > >     makes much
> > >
> > >     > >  sense. Also i tried to change Automount on login and Automount
> > >
> > >     on attach
> > >
> > >     > >  from No to Yes on my pendrive but wasn't able to do it.
> > >     >
> > >     > Multiple selection lets you forget more than one device at a
> > >     > time.
> > >
> > >     Also,
> > >
> > >     >  those two fields only change when the device list is rebuilt.
> > >     > I'm
> > >
> > >     thinking
> > >
> > >     >  I should build a model specifically for the KCM so that the
> > >
> > >     updating of
> > >
> > >     >  this is done when the checkboxes are toggled, and it'd be a lot
> > >
> > >     cleaner
> > >
> > >     >  than just a qstandardmodel.
> > >
> > >     Ok, makes sense, thanks for the clarification.
> > >
> > >     Albert
> > >
> > >     > > Albert
> > >
> > >     ------------------------------
> > >
> > >     Message: 4
> > >     Date: Wed, 4 Nov 2009 17:14:03 -0300
> > >     From: Dar?o Andr?s <andresbajotierra@...
> > >     <mailto:andresbajotierra@...>>
> > >     Subject: Re: Bugreporting barrier is too low with the new Dr. Konqi
> > >     To: KDE-Devel <kde-core-devel@...
> > > <mailto:kde-core-devel@...
> > >
> > >     Message-ID:
> > >            <a2c126ef0911041214n5613e97cv2ff945f1994cb28f@...
> > >     <mailto:a2c126ef0911041214n5613e97cv2ff945f1994cb28f@...
> > >
> > >     Content-Type: text/plain; charset=ISO-8859-1
> > >
> > >     Ok, I have currently implemented some features in order to improve
> >
> > the
> >
> > >     situation:
> > >
> > >     - The duplicate list that DrKonqi provides should be smarter and a
> >
> > bit
> >
> > >     smaller (as it uses a stricter query to bugzilla)
> > >     - The duplicate list now includes the bug status in a tag, with
> > >     no-jargon (ex ."[Open]", "[Fixed]", "[Already Reported]",
> >
> > "[Invalid]")
> >
> > >     - When you want to open a possible duplicate report, if that report
> > >     "X" is already marked as duplicate of another report "Z", you can
> > >     choose to show the report you wanted to open ("X") or the main
> > > report ("Z") <- Resolving nested duplicate levels
> > >
> > >     Other fixes that I have coded but I haven't commited yet:
> > >
> > >     - If there are possible duplicates listed and the user didn't
> >
> > selected
> >
> > >     anyone, nor marked anyone to attach the new information to it, a
> > >     messagebox will appear asking if he is sure.
> > >
> > >     - In the description step, if the user haven't entered a proper
> >
> > amount
> >
> > >     of input, the user is *forced* to do so (we need to discuss the
> >
> > amount
> >
> > >     of characters to be considered good input) (the user already
> > > selected the checkbox "I can provide information about the crash"). If
> > > the
> >
> > user
> >
> > >     doesn't accept this, the dialog is closed (but a warning about the
> > >     dialog being closed appears, if the user changes his/her mind...)
> > >
> > >     In both messages I'm explicitly saying that not following this
> >
> > advices
> >
> > >     will *waste* the time of the KDE developers and triagers, so at
> > > least they can think a bit before sending pseudo-crap. (yes, the text
> > > needs to be improved, may be it is too harsh...)
> > >
> > >     Screenshots of earlier implementation of this features:
> > >
> > >     http://imagebin.ca/view/XY3uu1W.html
> > >     http://imagebin.ca/view/i2-0cQ.html
> > >     http://imagebin.ca/view/0jSX7VP.html
> > >
> > >     I would like to get some feedback about all this things
> > >
> > >     Thanks in advance.
> > >     Regards
> > >
> > >     Dar?o A.
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 5
> > >     Date: Wed, 4 Nov 2009 21:32:09 +0100
> > >     From: Sebastian Tr?g <trueg@... <mailto:trueg@...>>
> > >     Subject: Re: [newbie]: Problems compiling kdebase-4.3 due to trig
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042132.09880.trueg@...
> > >     <mailto:200911042132.09880.trueg@...>>
> > >     Content-Type: Text/Plain;  charset="iso-8859-15"
> > >
> > >     which version of libredland and libraptor do you have installed?
> > >
> > >     On Tuesday 03 November 2009 22:58:14 Abhinav Chaturvedi wrote:
> > >     > Hi all,
> > >     >
> > >     > I am having problems compiling kdebase (of KDE-4.3 branch) and
> > >     > its
> > >
> > >     seems to
> > >
> > >     > because of nepomuk.
> > >     > i downloaded soprano-2.3.1 from sourceforge.net
> > >
> > >     <http://sourceforge.net>, compiled it and installed
> > >
> > >     > it in /usr/local.
> > >     > Hence, when I do cmakekde in kdebase, I get the following
> > >     > message:
> > >     >
> > >     >
> > >     > Found Soprano Plugin Dir: /usr/local/share/soprano/
> > >     > plugins/soprano/plugins
> > >     > -- Found Soprano Plugins: nquadparser nquadserializer
> > >     > raptorparser raptorserializer redlandbackend sesame2backend
> > >     >
> > >     > There is no 'trig'. I am assuming there should be a parser for it
> >
> > like
> >
> > >     >  there are for raptor, redland etc.
> > >     > And that this parser should have been included in Soprano-2.3.1.
> >
> > But
> >
> > >     > apparently it is not. Which is why
> > >     > I get the following message when compiling kdebase.
> > >     >
> > >     > [ 10%] Generating nie.h,
> > >     > nie.cpp
> > >     >
> > >     > Could not find parser plugin for encoding
> > >     > trig
> > >     >
> > >     > make[2]: *** [runtime/nepomuk/strigibackend/nie.h] Error
> > >     > 1
> > >     > make[1]: ***
> > >     > [runtime/nepomuk/strigibackend/CMakeFiles/sopranobackend.dir/all]
> > >
> > >     Error
> > >
> > >     > 2
> > >     > make[1]: *** Waiting for unfinished
> > >     > jobs....
> > >     >
> > >     > Linking CXX executable
> > >     > knotify4
> > >     >
> > >     > [ 10%] Built target
> > >     > knotify
> > >     >
> > >     > make: *** [all] Error 2
> > >     >
> > >     >
> > >     > I was wondering if you have seen this problem before. I must tell
> > >
> > >     you that
> > >
> > >     >  I did *not* checkout anything other
> > >     > than kdepimlibs, kdebase, kdelibs and phonon. These were enough
> >
> > when I
> >
> > >     >  tried compiling KDE-4.3 some
> > >     > months back.
> > >     >
> > >     > Is there anyway in which I can bypass 'nepomuk' compilation
> > >
> > >     altogether?
> > >
> > >     > If not, then how can I solve the above problem? Do I need to
> > >
> > >     checkout some
> > >
> > >     > other KDE packages?
> > >     >
> > >     > Thanks for your help
> > >     > Abhinav.
> > >
> > >     ------------------------------
> > >
> > >     Message: 6
> > >     Date: Wed, 4 Nov 2009 22:33:21 +0200
> > >     From: Olivier Goffart <ogoffart@... <mailto:ogoffart@...>>
> > >     Subject: Re: Qt KDE integration in kdereview.
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042133.21442.ogoffart@...
> > >     <mailto:200911042133.21442.ogoffart@...>>
> > >     Content-Type: Text/Plain;  charset="iso-8859-1"
> > >
> > >     Le Wednesday 04 November 2009, Diego Iastrubni a ?crit :
> > >     > making a KMainWindow, from a QMainWindow should be difficult.
> > >
> > >     However, one
> > >
> > >     >  of the most missing features for me in QToolBars are the
> > >     > icon/text settings and the lock toolbars command.
> > >     >
> > >     > I am just thinking aloud: how hard can this be?
> > >
> > >     Regarding the icon/text settings in a QToolBar:
> > >     - The default icon size is read from the KDE config for the default
> > >     KDE icon
> > >     size in toolba
> > >     - The default text position is read from the KDE config if using
> > >     Qt::ToolButtonFollowStyle  as QToolBar::toolButtonStyle  (new in
> > >     4.6, we could
> > >     not make it the default because it was a too huge behaviour change)
> > >
> > >     There is currently no plan to support being able to edit QToolBar
> > > as KDE does.
> > >
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 7
> > >     Date: Wed, 4 Nov 2009 21:53:25 +0100
> > >     From: Alexander Neundorf <neundorf@... <mailto:neundorf@...
> > >
> > >     Subject: Re: KDE is not an OS platform... (And neither is Gnome)
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042153.25201.neundorf@...
> > >     <mailto:200911042153.25201.neundorf@...>>
> > >     Content-Type: text/plain;  charset="iso-8859-1"
> > >
> > >     On Wednesday 04 November 2009, David Faure wrote:
> > >     > On Wednesday 04 November 2009, nf2 wrote:
> > >     > > * But Qt-only apps?
> > >     > >
> > >     > > And i do believe Qt is quite important for getting more apps
> >
> > written
> >
> > >     > > for the FOSS desktop. As its portability is very attractive.
> > >     >
> > >     > OK, that's a good point. However QFile/QDir is not the answer
> > >     > IMHO. Qt has a nice API for async networking requests already:
> > >     > QNetworkAccessManager (for which we have a KIO backend; the
> > >     > qt-kde
> > >
> > >     platform
> > >
> > >     > plugin (cf the thread from Olivier) could even use that when
> > >
> > >     kdelibs is
> > >
> > >     > around).
> > >     > But for file dialogs, it misses directory listing, and stat, at
> >
> > least.
> >
> > >     I think QAbstractFileEngine comes quite close, you can use to to
> > > plug in "virtual" filesystems based on URLs into Qt apps, including the
> >
> > file
> >
> > >     dialog.
> > >
> > >     Alex
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 8
> > >     Date: Wed, 4 Nov 2009 21:59:54 +0100
> > >     From: Alexander Neundorf <neundorf@... <mailto:neundorf@...
> > >
> > >     Subject: Re: Qt KDE integration in kdereview.
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID: <200911042159.54853.neundorf@...
> > >     <mailto:200911042159.54853.neundorf@...>>
> > >     Content-Type: text/plain;  charset="iso-8859-1"
> > >
> > >     On Wednesday 04 November 2009, David Faure wrote:
> > >     > On Wednesday 04 November 2009, George Kiagiadakis wrote:
> > >     > > On Wed, Nov 4, 2009 at 3:19 AM, David Faure <faure@...
> > >
> > >     <mailto:faure@...>> wrote:
> > >     > > > On Wednesday 04 November 2009, Michael Pyne wrote:
> > >     > > >> On Tuesday 03 November 2009 17:10:19 Kevin Krammer wrote:
> > >     > > >> > Maybe startkde could set KDEHOME to localprefix if it is
> > >
> > >     not set
> > >
> > >     > > >> > yet?
> > >     > > >>
> > >     > > >> That wouldn't be a bad idea either, it's easier just to
> > >
> > >     always have
> > >
> > >     > > >> KDEHOME set than special-casing it.
> > >     > > >
> > >     > > > Yep, excellent idea.
> > >     > >
> > >     > > No, bad idea. If you are using both kde3 and kde4 apps and you
> >
> > want
> >
> > >     > > them to use different KDEHOMEs, setting KDEHOME in startkde is
> >
> > just
> >
> > >     > > going to force them both to use the same KDEHOME, which is not
> > >
> > >     what we
> > >
> > >     > > want.
> > >     >
> > >     > True.
> > >     > And I just realized that it wouldn't help making sure KDEHOME is
> > >
> > >     always
> > >
> > >     > set, since one can also run kde apps outside of a kde workspace
> > >     > (->
> >
> > no
> >
> > >     > startkde run).
> > >     >
> > >     > > That's why the KDE4_DEFAULT_HOME cmake variable exists.
> > >     >
> > >     > Yeah but that's not introspectable.
> > >     > Hmm, actually, it is:  `kde4-config --localprefix`, but calling a
> > >
> > >     process
> > >
> > >     > probably too slow for doing from Qt?
> > >
> > >     Hmm, if it's done once on application startup it might be
> > > acceptable.
> > >
> > >     It's also saved in
> > >     share/apps/cmake/modules/KDELibsDependencies.cmake, in the
> > >     KDE_DEFAULT_HOME variable.
> > >     You can basically rely on the format of that line:
> > >     set(KDE_DEFAULT_HOME ".kde")
> > >     So without really parsing it just matching a regexp should do.
> > >
> > >     Alex
> > >
> > >
> > >     ------------------------------
> > >
> > >     Message: 9
> > >     Date: Wed, 4 Nov 2009 20:48:04 -0200
> > >     From: Tomaz Canabrava <tumaix@... <mailto:tumaix@...>>
> > >     Subject: Re: Rocs moved to kdereview.
> > >     To: kde-core-devel@... <mailto:kde-core-devel@...>
> > >     Message-ID:
> > >            <7ebbb4b50911041448g42da8498gf938ec5aae8436f8@...
> > >     <mailto:7ebbb4b50911041448g42da8498gf938ec5aae8436f8@...
> > >
> > >     Content-Type: text/plain; charset=ISO-8859-1
> > >
> > >     Ok, I'v managed to fix 2 crashes, workarounding a well known
> > >     qt-problem on trees & graphicsview.
> > >     it shoudn't crash no more.
> > >
> > >     and improved the showing of the properties of the nodes and edges.
> > >
> > >     tomorrow I will do nothing ( beach time ), but I plan to have
> > >     everything that anyone say here fixed by next sunday.
> > >
> > >
> > >     ------------------------------
> > >
> > >     _______________________________________________
> > >     kde-core-devel mailing list
> > >     kde-core-devel@... <mailto:kde-core-devel@...>
> > >     https://mail.kde.org/mailman/listinfo/kde-core-devel
> > >
> > >
> > >     End of kde-core-devel Digest, Vol 80, Issue 27
> > >     **********************************************
> > >
> > >
> > >
> > >
> > > --
> > > It's the peoples' will, I am their leader, I must follow them. (Jim
> > > Hacker in Yes Minister)
> >
> > ------------------------------
> >
> > _______________________________________________
> > kde-core-devel mailing list
> > kde-core-devel@...
> > https://mail.kde.org/mailman/listinfo/kde-core-devel
> >
> >
> > End of kde-core-devel Digest, Vol 80, Issue 43
> > **********************************************
>

Re: [Sebastian Treug] Problems compiling kdebase-4.3 due to trig

by Alexander Neundorf :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tuesday 10 November 2009, Sebastian Trüg wrote:
> Please state the actual problem again as the email history does not seem to
> contain it...

I may have the same problem:
http://my.cdash.org/viewBuildError.php?buildid=37719

That's the full output:

[ 94%] Generating nie.h, nie.cpp
cd "/home/alex/Dashboards/kdelibs/build dir-Linux-cmake-2.6.2/nepomuk/query"
&& /home/alex/Dashboards/installs/2.6.2/kdesupport/bin/onto2vocabularyclass --name
NIE --encoding trig --namespace
Nepomuk::Vocabulary --no-visibility-export /home/alex/Dashboards/kdelibs/src\
dir/nepomuk/query/nie.trig
Could not find parser plugin for encoding trig
make[2]: *** [nepomuk/query/nie.h] Error 1



Do I have to install something named "trig" ?
Or is the right "trig"-plugin installed but onto2vocabularyclass can't find
it ?


kdesupport is in ~/installs/kdesupport/, kdelibs will go to
~/installs/kdelibs/.

Alex