On Thursday 15 March 2007 04:36, Alan DuBoff wrote: > Kfolk, (I know there's only a couple of you;-) > > The question of where to begin for getting a KDE build for > OpenSolaris. > > If I understand correctly, KDE 4.x will be the first version to > support Solaris. I'm not exactly sure what that means, maybe Stefan > can elaborate on what that does exactly mean, or someone else if > one you do.
What it means: with KDE4, Solaris/SunStudio are supported at KDE. KDE3 did not fully support it, in the sense that the primary development platform was Linux and GCC. On KDE3, Solaris was supported to the extent KDE dudes were willing to spend the time to make it work. > It seems to me that if KDE 4.x will support Solaris, it might be > wise to bite the bullet, go for the latest code, and use what we > have in the meantime. The KDE Foundation (KDE e.V.) gave the Green Light for Solaris to become one of the supported OS's (supported as opposed to ported). However, KDE4 on Solaris will become reality only to the extent OpenSolaris folks (us) are willing to invest the time to work on it. The KDE Foundation gave the green light for Solaris support. The reality still is that the development expertise in the open source world is still Linux. The development expertise on Solaris is here. It's up to us to make Solaris on par with Linux. > I do want to get a more recent build than I'm using, and most > machines I'm using 3.1.1, the old and crusty (but reliable) from > the ccd that Paul Cunningham built when he was with Sun. There's 3.4.3 from http://solaris.kde.org/. Blastwave has more recent KDE's as well. > I also have a 3.3.1 running on a sparc box at home, but it's fairly > dated also. And i bet it doesn't have anti-aliased fonts. :-) > Does someone know if 4.x run yet on other platforms? Must run on > Linux by now I would think. "Technical preview". Not there yet. It's buildable on Linux. IMHO: KDE4 is a longer term project. To get there, we still have to build tons of extra libraries on which KDE depends, before we can start building KDE. These libraries aren't even in Nevada. I think it would be more practical to work in parallel on 3.5.5 and KDE4. It might very well be that it will take until KDE 4.0.2 before the Solaris version of KDE4 is up to Sun standards. Maybe we should have a 3.5.5 build ready before that (3.5.5 is really nice). A lot of the work required is common between the two. There is one major feature i would like to add in KDE 3 and 4: CORBA bindings to replace DCOP. We can use omniORB (http://omniorb.sourceforge.net/). It runs perfectly on Solaris 32- and 64- bit. There are technical reason behind this pet peeve of mine, and i have the benchmark study done by someone else to back me up. :-) KDE4 uses CMake (http://www.cmake.org/) for its build system. The auto tools are no longer used. This is good and bad. Good because we don't have to deal with libtool in KDE4, and CMake is much nicer. Bad because we still have to deal with libtool for all the other dependencies. A while ago i put together a list of KDE dependencies -- i will dig it up and post it here. This list is very long. QT 3.3.7 and 4.2.2 are here: http://svn2.cvsdude.com/kdesolaris/trunk/QT/3.3.7 http://svn2.cvsdude.com/kdesolaris/trunk/QT/4.2.2 svn co --username=anonymous http://svn2.cvsdude.com/kdesolaris/trunk CVSDude is our sandbox (courtesy of yours truly). The agreement i have with KDE e.V. is that all our source code *must* be committed upstream, eventually, in KDE SVN. If we don't keep our promise, they will get very very mad. :-) We can use CVSDude for work-in-progress, and if we break the builds, Dirk Mueller and Stephan Kulow won't know and won't flame us :-). --Stefan -- Stefan Teleman 'Nobody Expects the Spanish Inquisition' KDE e.V. -Monty Python stefan.teleman at gmail.com
