habacker added a comment.
Sorry for the two spam comments, I had a freeze at phabricator web site. > Here's the android scripts for reference. https://cgit.kde.org/sysadmin/ci-tooling.git/tree/system-images/android/sdk 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 https://build.opensuse.org/project/show/KDE:Frameworks5. From working on the kf5 packages on obs I know that this approach has some issues: 1. Not all required tools are installed with the package - I needed dedicated patches to let packages install them too (at least) - https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/kdoctools-17 - https://build.opensuse.org/package/show/home:rhabacker:branches:KDE:Frameworks5/sonnet-17 2. From memory I remember that not all KF5 packages have working cross compile support 3. obs uses currently another approach - there is a cross kf5 tools package providing all required tools installed in a custom location in one package (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). 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 https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-kf5-filesystem/macros.mingw32-kf5?expand=1 REPOSITORY R237 KConfig REVISION DETAIL https://phabricator.kde.org/D9387 To: habacker, dfaure, ltoscano, bcooksley, apol Cc: kde-frameworks-devel, apol, michaelh, ngraham, bruns
