https://bugs.kde.org/show_bug.cgi?id=430402
--- Comment #2 from Dirk Hohndel <d...@hohndel.org> --- (In reply to Nicolas Fella from comment #1) > > on https://api.kde.org/frameworks/index.html iOS support is marked with > "maintainer needed", which describes the state pretty well I think. Thanks for pointing that out - I didn't realize this. The main reason that my project adopted Kirigami almost 5 years(!) ago was to have support for both Android and iOS from the same code base. So to us iOS support is critically important. > From my limited understanding there is no major reason why it wouldn't work. I was able to hack things together with a little more experimentation in order to get it to compile and am able to build the library for iOS now. I can only get it to work with qmake, and only if I don't follow the model that is used in many other places in the examples to include the kirigami.pri file - that simply doesn't work. But if I use qmake to build Kirigami as a separate library using the .pro file, that seems to do the trick. I guess I should submit the beginning of a README.iOS or something like this to document that fact for the next person who comes around :-) > You're right, there currently is no CI coverage for iOS (no KDE project has > as far as I know). There are some major changes to the CI infrastructure > upcoming and that may make it easier to provide that, assuming there is > interest in it at all. I'd be very interested in seeing that. Subsurface builds for iOS on every pull request / merge using GitHub Actions. I'm less familiar with the GitLab CI infrastructure, but getting something in place that ensures this doesn't get broken would be nice. Of course, we have about a dozen patches to Kirigami that deal with some of our preferences - most of them would likely be challenging to upstream as they tend to be things where we just disagree with the way Kirigami does things. But none of them should have any impact on the "buildability" of Kirigami for iOS. > I assume most of the people currently involved lack the interest or means > (e.g. access to apple hardware) to do meaningful work here. That said I'm > sure input from people that have an interest in Kirigami (other other KDE > software) is welcome and appreciated. I'd be very interested to understand if there are any active Kirigami developers with access to a Mac with new enough software to build current iOS binaries and at least one iOS device to test things with... -- You are receiving this mail because: You are watching all bug changes.
