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

List:       kde-buildsystem
Subject:    Re: Buildsystem TODO list
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2011-08-23 17:35:41
Message-ID: 201108231935.41431.neundorf () kde ! org
[Download RAW message or body]

On Tuesday 23 August 2011, Raphael Kubo da Costa wrote:
> "Yury G.  Kudryashov" <urkud.urkud@gmail.com> writes:
> > Raphael Kubo da Costa wrote:
> > 
> > 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.
> 
> This could work, but is the second part really necessary? If only
> ProjectNameConfig.cmake exists and the application using it does not
> have its own FindProjectName.cmake, when it calls
> find_package(ProjectName) CMake would find ProjectNameConfig.cmake
> anyway.

A nice feature of having a Find-file, even if it only does 
find_package(NO_MODULE), is that it can contain documentation about provided 
variables and macros.
It can also add additional search paths, maybe a nicer status message, etc.
It also makes explicit that we are searching for a Config.cmake file.

So I would recommend having such small find-files even for packages which 
install a Config.cmake file.

Alex
_______________________________________________
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]