Alexander Neundorf wrote:
> If some library needs some exotic library, it should be good enough if it
> contains the Find-module itself.
This wasn't on the wiki page. I added it with the recommendation that such
find modules shouldn't be installed.
__
On Saturday 18 February 2012, Kevin Ottens wrote:
> On Saturday 18 February 2012 17:35:14 Alexander Neundorf wrote:
> > On Saturday 18 February 2012, Kevin Ottens wrote:
> > > Sounds good to me. Worth putting in the directory policy?
> > > http://community.kde.org/Frameworks/Policies#Framework_dire
On Saturday 18 February 2012 17:35:14 Alexander Neundorf wrote:
> On Saturday 18 February 2012, Kevin Ottens wrote:
> > Sounds good to me. Worth putting in the directory policy?
> > http://community.kde.org/Frameworks/Policies#Framework_directory_structure
> >
> > We're basically saying nothing abo
On Saturday 18 February 2012, Kevin Ottens wrote:
> On Saturday 18 February 2012 17:09:55 Alexander Neundorf wrote:
> > in kdelibs we have the directory cmake/modules/, where we have all the
> > Find- modules.
> > Back then when we ported kdelibs to cmake I thought it would make sense
> > to put th
On Saturday 18 February 2012 17:09:55 Alexander Neundorf wrote:
> in kdelibs we have the directory cmake/modules/, where we have all the Find-
> modules.
> Back then when we ported kdelibs to cmake I thought it would make sense to
> put these modules into a subdirectory of cmake/, since there might
Hi,
in kdelibs we have the directory cmake/modules/, where we have all the Find-
modules.
Back then when we ported kdelibs to cmake I thought it would make sense to put
these modules into a subdirectory of cmake/, since there might come other
stuff.
Now, 6 years later, we can look back.
There w
