<div dir="ltr">On Tue, Sep 10, 2013 at 7:42 PM, Michael Palimaka <span dir="ltr"><<a href="mailto:kensington@gentoo.org" target="_blank">kensington@gentoo.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Currently, the specification for Qt dependencies is not always consistent between tier1 frameworks.<br>
<br>
In particular, I notice dependencies being specified twice (eg. QtTest in both project root and in autotests), and test dependencies split (eg. QtTest in project root only, and QtXml in autotests only).<br>
<br>
What is the intended behaviour? All dependencies specified in the project root? Common dependencies specified in the project root, and specific dependencies in directories that require them? Something else?<br>
<br>
Best regards,<br>
Michael<br>
<br>
______________________________<u></u>_________________<br>
Kde-frameworks-devel mailing list<br>
<a href="mailto:Kde-frameworks-devel@kde.org" target="_blank">Kde-frameworks-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-frameworks-devel" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/kde-frameworks-devel</a><br>
</blockquote></div><br></div><div class="gmail_extra">I'd say that all Qt dependencies in the module should be defined only once in the root CMakeLists.txt. Actually this should be the only file with "find_package" calls.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">We could try an be stricter, but in practice what is useful for distribution is the find_dependency call in the <a href="http://Config.cmake.in">Config.cmake.in</a> file...</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>