NOTE: Please refer to Get It for up-to-date Windows versions
It took some time but here is now an installer for Kate on Windows.
First the proof 🙂
There are still some things that needs fixing. The current installer is built from git master and not from released packages so the translation stuff hat you usually get with the release packages are missing. So only partially translated. Another feature that I’m still missing is the spell-check. I need to still add a/hspell and language dictionaries to get that to work.
You can use a plain Qt and current KDE Frameworks & Kate master to get that running. Guess the next goal would be to get KIO working without patching Qt, lets see how much work that is.
P.S. With the guide in mac.txt you should be able to try out how to port other KDE based applications, too, and get a application bundle, as most stuff should be available now, for the average application. How to use some bundled Breeze icon set can be found here, just call code like that after QApplication is constructed:
with my latest changes in kate.git, icons work, too, on windows and mac, without any qt patch, if you put some qt resource file containing breeze inside your share or Resources folder (one up from the application binary).
mac.txt contains the rcc calls needed to create such a package and all others things you need to run to get .dmg files. (you need Qt 5.5.0 + a recent CMake + XCode with command line stuff enabled)
Kate plugins should work, too, if you have a qt.conf that points to the local plugins (like macdeployqt will create for you in the mac.txt run).
Things not working ATM without patched Qt or more work: KIO slaves and all dbus related stuff.
With that in place, I consider Kate/KWrite on Mac at least of alpha quality. Still some plugins are missing, optimizations for the .dmg generation could be done like removing stuff we don’t use like QtWebKit from the bundle, but besides, the programs do something and don’t crash immediately, at least not on my Mac OS 10.10 installation.
Mandatory Screenshot :=)
Links to Kate & KWrite .dmg files: (ALPHA quality still, only tested on Mac OS 10.10, now just with icons and some plugins and too many Qt libraries and plugins to make the .dmg large 🙂
P.S. Testers are welcome, but help of any other kind even more 😉 Given Kate/KWrite are trivial to build on a Mac with just XCode around and the stuff described in mac.txt it would be really GREAT if somebody could step up to help to fine tune this to have some more usable beta or even “real” release for Mac in the future. I will continue to work on this, but my Mac isn’t my main working machine nor what I use for my daily company work, therefore, this is not my highest priority.
after one week of patching frameworks (and KWrite/Kate), the first success can be seen: a kind of working application bundle for KWrite.
Still no icons, need to set icon theme + search paths right and bundle that, too, but need to investigate more how the icon lookup works.
You can build the stuff on your own just following kate.git/mac.txt and calling once the macdeployqt tool afterwards on the /Applications/KDE/kwrite.app bundle (with -dmg to get the disk image file).
For Kate, the macdeployqt still misses an additional switch to deploy own plugins in addition, will add that in the next days, I hope. Have already some local hack, but want to have some patch I can hand in to Qt Company.
Here a link to the version you see above in the screenshot (not tested below Mac OS 10.10):
A colleague tested it for me on a Mac without any dbus/macports/homebrew/co. stuff installed and it seems to work and not eat all his data ;=) But this is ALPHA quality, this means all things can happen, I didn’t test it that much beside using it for my last kate.git commit and starting it up for that screenshot above, not more ;=)
The good things: This stuff needs no patched Qt nor any patches to any KF5 stuff, this uses plain Qt 5.5.0 from the Qt Company installer and all modifications for frameworks are inside our master branch of framworks already.
The bad things: e.g. KIO doesn’t work atm (even if the io slaves would be in the bundle), therefore only local file support.