KDE on Mac OS X has a long history, but is seeing new life in KDE4 and Qt4/Mac by bringing native KDE4 applications to the Mac OS X desktop.
If you are interested in installing KDE 3.x on Mac OS X, check out the KDE 3 page.
KDE 4.x on Mac OS X is quickly reaching a stable stage, and currently could be considered a "technology preview". Official support for Mac OS X is targeted for KDE 4.1.0.
Mac OS X is already a "desktop environment" in the sense that it provides window management, application launching, etc. The goal of KDE on Mac OS X is to provide the rich frameworks and applications in KDE to a wider audience.
In KDE 4, we intend to have:
Perhaps not all of these things will be available by 4.1, but the goal is to do as much as possible for release.
You must install at least Qt, kdesupport, and kdelibs for any of these packages to work. Note that kdelibs requires soprano and strigi. Also, kdepimlibs and kdebase are recommended since a number of things will want them. (...and it has Konqueror)
Please note: since most people tend to download the complete package, downloading everything is usually faster (if you have broadband, obviously). And don't forget to seed!
|requires kdelibs, kdesupport, qt, strigi (temporarily not building)|
|blitz||10.4/10.5||requires kdelibs, kdesupport, qt, strigi|
|decibel||10.4/10.5||requires kdelibs, kdesupport, qt|
|kdeadmin||10.4/10.5||requires kdelibs, kdepimlibs, qt, strigi|
|kdeartwork||10.4/10.5||requires kdelibs, qt|
|kdebase||10.4/10.5||requires blitz, kdelibs, kdepimlibs, kdesupport, qt, soprano, strigi|
|kdeedu||10.4/10.5||requires kdelibs, kdesupport, qt, strigi|
|kdegames||10.4/10.5||requires kdelibs, kdesupport, qt, strigi|
|kdegraphics||10.4/10.5||requires blitz, kdelibs, kdesupport, qt, strigi|
|kdelibs||10.4/10.5||requires kdesupport, qt, soprano, strigi|
|kdemultimedia||10.4/10.5||requires kdelibs, kdesupport, qt, strigi|
|kdenetwork||10.4/10.5||requires kdelibs, kdepimlibs, kdesupport, qt, strigi|
|requires kdelibs, kdepimlibs, kdesupport, qt, strigi (not included in KDE 4.0)|
|kdepimlibs||10.4/10.5||requires kdelibs, qt, strigi|
|kdesdk||10.4/10.5||requires kdelibs, kdepimlibs, kdesupport, qt, strigi|
|kdetoys||10.4/10.5||requires kdelibs, qt, strigi|
|kdeutils||10.4/10.5||requires kdelibs, kdepimlibs, qt, strigi|
|requires kdelibs, kdevplatform, qt, strigi (not included in KDE 4.0)|
|kdevplatform||10.4/10.5||requires kdelibs, qt, strigi|
|kdewebdev||10.4/10.5||requires kdelibs, kdesupport, qt, strigi|
|koffice||10.4/10.5||requires blitz, kdelibs, kdepimlibs, kdesupport, qt, strigi|
|qt-extras||10.4/10.5||requires kdesupport, qt|
|soprano||10.4/10.5||requires kdesupport, qt|
|strigi||10.4/10.5||requires kdesupport, qt|
If you want to compile against these snapshots, you also need cmake. You can get the latest release from their download page.
Running apps should usually work from Finder. But if for some reason they don't, you can try these two steps:
From the command line, update PATH and launch dbus, like so:
export PATH="/opt/kde4/bin:/opt/kde4-deps/bin:/opt/qt4/bin:$PATH" eval `dbus-launch --auto-syntax`
Then, to start an app, you call it from the same terminal, like this:
NOTE: Don't try to start the 'real' binary directly, like so:
since this will result in various interactions with the OS (drag and drop, for example) not working.
Sometimes, Installer.app fails to run the post-install. Try running:
...and see if your application starts.
友情链接交换站点:国际机票 国内机票 搬家公司 北京搬家公司 搬家搬家公司 北京搬家 北京搬家公司 婚纱 礼服 婚纱摄影 胶带 圣诞树 小本创业 条码打印机 证卡打印机 证卡机 标签打印机 吊牌打印机投影机 投影仪 月嫂 育儿嫂月嫂 育儿嫂 月嫂 育儿嫂 婴儿用品 宝石 眩晕 咖啡机 逆变器 北京油烟净化器 营养师考试 橡胶模 电子产品设计 公共营养师 自动麻将桌 空调保养 北京婚庆 北京婚庆 机床厂 麻将机 打印机维修 肩周炎 镇流器 空调安装 塑钢门窗 强直性脊柱炎 空调移机 空调移机 北京空调移机 门禁系统 蛋糕 北京空调维修 治疗近视 eq2 gold 营养师资格考试 门禁 电话交换机 集团电话 前列腺 前列腺炎 前列腺炎症 前列腺增生 慢性前列腺炎 急性前列腺炎 前列腺癌 前列腺肥大 前列腺症状 前列腺治疗 前列腺痛 细菌性前列腺炎 前列腺发炎 前列腺炎检查 前列腺疾病 早泄 阳痿 泌尿 血尿 尿路感染打扰了!
If you'd like to try building KDE yourself, it should (mostly) work out of the box. You can get tips on building here (including a link to the tools I use to generate these packages).
There's still a lot to do. I'm going to try to keep a running list of what needs to be done on the TODO page.
You can find the KDE4/Mac developers in the #kde-mac IRC channel on FreeNode and folks working on KDE4 in general in the #kde-devel channel. This should be the first place you look. If you have a question, be patient, sometimes we're logged in but not looking at IRC all the time. If you stick around, we'll answer.
The official list for KDE/Mac development is firstname.lastname@example.org.
There are lots of great mailing lists for more general KDE discussion. For a complete list, see the KDE mailing list page. The KDE/Mac developers have been known to hang out on kde-buildsystem, kde-devel, and kde-nonlinux.
First of all, before doing anything else, check the KDE bug page to see if your problem has already been reported. If so, add as much as you can to the existing bug report to make it easier for developers to figure out what's gone wrong.
You might also want to try the IRC channel(s) before filing a bug, you're more likely to get a quick response there. Also be aware, we know there's still stuff broken on Mac OS X, so be gentle. :)