<table><tr><td style="">habacker added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D9387">View Revision</a></tr></table><br /><div><div><p>Sorry for the two spam comments, I had a freeze at phabricator web site.</p>

<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Here's the android scripts for reference. <a href="https://cgit.kde.org/sysadmin/ci-tooling.git/tree/system-images/android/sdk" class="remarkup-link" target="_blank" rel="noreferrer">https://cgit.kde.org/sysadmin/ci-tooling.git/tree/system-images/android/sdk</a></p></blockquote>

<p>Ah I see, on Android the packages containing native tools are build. The package and their development packages including the cmake support files (xxxTargets.cmake)  are then installed to a custom destination  to which KF5_HOST_TOOLING is pointing to. Transformed to obs that would mean to use the runtime and development packages from <a href="https://build.opensuse.org/project/show/KDE:Frameworks5" class="remarkup-link" target="_blank" rel="noreferrer">https://build.opensuse.org/project/show/KDE:Frameworks5</a>.</p>

<p>From working on the kf5 packages on obs I know that this approach has some issues:</p>

<ol class="remarkup-list">
<li class="remarkup-list-item">Not all required tools are installed with the package - I needed dedicated patches to let packages install them too (at least)<ul class="remarkup-list">
<li class="remarkup-list-item"><a href="https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/kdoctools-17" class="remarkup-link" target="_blank" rel="noreferrer">https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/kdoctools-17</a></li>
<li class="remarkup-list-item"><a href="https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/sonnet-17" class="remarkup-link" target="_blank" rel="noreferrer">https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/sonnet-17</a></li>
</ul></li>
<li class="remarkup-list-item">From memory  I remember that not  all KF5 packages have working cross compile support</li>
<li class="remarkup-list-item">obs uses currently another approach - there is a cross kf5 tools package providing all required tools installed in a custom location in one package (<a href="https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-cross-kf5-tools/mingw32-cross-kf5-tools.spec?expand=1" class="remarkup-link" target="_blank" rel="noreferrer">https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-cross-kf5-tools/mingw32-cross-kf5-tools.spec?expand=1</a>). This behavior is derived from the related xxx-cross-libqt5-yyy package. The native tools are installed as mingw helper tools and used in the cmake command line <a href="https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-kf5-filesystem/macros.mingw32-kf5?expand=1" class="remarkup-link" target="_blank" rel="noreferrer">https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-kf5-filesystem/macros.mingw32-kf5?expand=1</a></li>
</ol>

</div></div><br /><div><strong>REPOSITORY</strong><div><div>R237 KConfig</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D9387">https://phabricator.kde.org/D9387</a></div></div><br /><div><strong>To: </strong>habacker, dfaure, ltoscano, bcooksley, apol<br /><strong>Cc: </strong>kde-frameworks-devel, apol, michaelh, ngraham, bruns<br /></div>