[cmake-developers] Should a module attempt to find its own dependencies?

Hi, I don't think I've ever seen a direct answer to this question. Is it something to be decided on a case by case basis? If so, then why is there no general case? I can see a possible reason that it is not solvable in the general case because sometimes the behaviour of find_package can be

Re: [cmake-developers] Should a module attempt to find its own dependencies?

Alexander Neundorf wrote: On Sunday 08 January 2012, Stephen Kelly wrote: Hi, I don't think I've ever seen a direct answer to this question. AFAIK, yes, they should. FindKDE4Internal.cmake finds Qt, FindPNG.cmake finds zlib. Is it something to be decided on a case by case basis? If

Re: [cmake-developers] Should a module attempt to find its own dependencies?

On Sunday 08 January 2012, Stephen Kelly wrote: Alexander Neundorf wrote: On Sunday 08 January 2012, Stephen Kelly wrote: Hi, I don't think I've ever seen a direct answer to this question. AFAIK, yes, they should. FindKDE4Internal.cmake finds Qt, FindPNG.cmake finds zlib. Is

Re: [cmake-developers] Should a module attempt to find its own dependencies?

On 01/09/2012 03:07 AM, David Cole wrote: On Sunday, January 8, 2012, Alexander Neundorf neund...@kde.org mailto:neund...@kde.org wrote: On Sunday 08 January 2012, Stephen Kelly wrote: Alexander Neundorf wrote: On Sunday 08 January 2012, Stephen Kelly wrote: Hi, I don't think I've