Buildsystem TODO list

[Michael Jansen]

On Tuesday, August 23, 2011 08:39:33 PM Alexander Neundorf wrote:
> On Tuesday 23 August 2011, Michael Jansen wrote:
> > On Tuesday, August 23, 2011 07:35:41 PM Alexander Neundorf wrote:
> > > On Tuesday 23 August 2011, Raphael Kubo da Costa wrote:
> > > > "Yury G.  Kudryashov" <urkud.urkud at 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,
> > 
> > NO WAY ... Everything else i wholeheartily agree. But this? ... NO WAY
> 
> Why not ?
> CMAKE_PREFIX_PATH will still be prefered.
> (and when using PATHS instead of HINTS it would be checked after everything
> else)

But it WOULD BE CHECKED. That is all to say. I can't control anymore where it 
looks.

Mike