mahiwaga

I have embarked on a quest to compile KDE against QT/Mac so that I can run KDE apps natively instead of running them with X.

I finally got QT to compile cleanly, using the instructions on how to compile QT/Mac by Ranger Rick as a reference. I don't know if the instructions don't work exactly as stated because Qt/Mac is no longer beta, or if there are other reasons, but what I did was somewhat different (NOTE: I will assume that you are very comfortable with the command-line and have some experience with compiling from source):

1. Untar the archive to whereever you want, such as in ~/.
2. Set $QTDIR to point to whereever you unpacked the archive. For example, ~/qt-mac-free-3
3. Add $QTDIR/bin to $PATH
4. Add $QTDIR/lib to $DYLD_LIBRARY_PATH
5. ./configure --prefix=/opt/qt-mac
6. make
7. sudo make install
8. Change $QTDIR to /opt/qt-mac
9. Reset $PATH, $MANPATH, and $DYLD_LIBRARY_PATH to reflect the change in $QTDIR

in the ongoing saga of getting KDE to build against QT/Mac, I have been following Ranger Rick's instructions on how to build KDE against QT/Mac yourself. the first hurdle was arts. after some kludgery, I came up with this configure command:

LDFLAGS="-lXi -lXmu -lm -lXext -lX11 -L/usr/X11R6/lib" CFLAGS="-Os" CXXFLAGS="-Os" ./configure --prefix=/opt/kde --with-qt-dir=/opt/qt-mac --with-extra-libs=/sw/lib --with-extra-includes=/sw/include --enable-mac

I won't claim to understand everything that's going on here. The CXXFLAGS are necessary to keep the atomicity.h error, also found in other applications, from happening. The LDFLAGS are necessary so that arts can find X11(?!) I don't know why the code depends on both glib and X11 despite being based on Qt/Mac, but, hey, it compiles.

in trying to configure kdelibs, I ran across this problem with net/if.h (which is, again, present in other applications being ported to OSX)

a patch to config.in.in allows configure to succeed without warnings.

after applying the patch, run make -f admin/Makefile.common cvs

now to see if it compiles.

of course, to save much pain and misery, you can use the scripts provided by Ranger Rick for building KDE, which includes configure-kde, which will figure out the proper flags and library locations for you. He also included some patches, but I haven't gotten them to apply cleanly to the CVS versions of the kde modules.