[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-buildsystem
Subject:    Re: Buildsystem TODO list
From:       "Yury G.  Kudryashov" <urkud.urkud () gmail ! com>
Date:       2011-08-23 12:46:04
Message-ID: j307ec$or7$1 () dough ! gmane ! org
[Download RAW message or body]

Raphael Kubo da Costa wrote:

> Alexander Neundorf <neundorf@kde.org> writes:
> 
>> --------------------------------------------------------
>> Take care of Strigi, Nepomuk & Soprano buildsystem-wise
>> --------------------------------------------------------
>>
>> Allen wrote last week to kde-buildsystem that there are multiple
>> FindSoprano.cmake files, they differ and they need work.
>> I would add that personally I'm still somewhat confused by Strigi,
>> Nepomuk, Soprano, Raptor, Virtuoso and friends, and since they all belong
>> somehow together, it would be nice if somebody would volunteer to take
>> care of the cmake stuff for them.
>> This means:
>> - take care of the Find-modules
>> - the projects themselves (Strigi, Nepomuk, Soprano) should install
>> Config.cmake files to help with finding them
>> - keep an eye on which of those packages are optional to kdelibs/parts of
>> KDE frameworks and make that work properly
> 
> Should the projects under KDE (Strigi, Nepomuk, Soprano) only install
> Config.cmake files so that we only provide Find* files for the ones over
> which we do not have much contorl (Raptor, Virtuoso etc)?
As far as I understand, the proposed scenario for projects with cmake-based 
buildsystem is:
 * the project itself installs ProjectNameConfig.cmake;
 * ecm (or cmake) distribute a short FindProject.cmake that calls 
find_package(ProjectName ... NO_MODULE ...)

One of the examples is kdepimlibs.
-- 
Yury G. Kudryashov,
mailto: urkud@mccme.ru

_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
[prev in list] [next in list] [prev in thread] [next in thread]