[RFC] cmake modules and keeping source compatibility

Alexander Neundorf neundorf at kde.org
Sat Jan 19 18:54:30 GMT 2008


On Saturday 19 January 2008, Christian Ehrlicher wrote:
> Alex Merry schrieb:
> > At Friday 18 January 2008 18:17, you wrote:
> >> A better approach would be not to hardcode the required version in the
> >> cmake module, but to set it from the outside:
> >>
> >> set(SOPRANO_REQUIRED_VERSION 2.0)
> >> find_package(Soprano REQUIRED)
> >>
> >> and then compare with SOPRANO_REQUIRED_VERSION in FindSoprano.cmake.
> >
> > Wouldn't it be sensible to do this with all packages?  It would make the
> > modules more useful for other projects, both inside (by using the
> > installed versions) and outside (by copying the files) KDE.
>
> +1
>
> but we should sync this with the cmake devs to avoid naming confusion
> like foo_LIBRARY <-> foo_LIBRARIES and others.

Yes for both (actually I try to do this, but it's kind of hard if it's for a 
package where you know yourself nothing about)

Alex




More information about the kde-core-devel mailing list