[kde-freebsd] KDE4 apps porting questions

Max Brazhnikov makc at issp.ac.ru
Sun Oct 5 17:33:55 CEST 2008

On Sun, 5 Oct 2008 04:43:40 -0400, Jason E. Hale wrote:
> I am in the process of porting a few simple plasma applets and I don't have
> much to go on since there aren't many example ports for KDE4 specific apps
> yet.  Basically, they all compile fine and the ports work the way I have
> them, but my questions are more about proper ports structure.
> 1) If I have a line like:
> USE_KDE4=       automoc4 kdeprefix workspace
> Is it necessary to include the QT4 components as well even though these get
> pulled in by the KDE4 components:
> USE_QT_VER=     4
> QT_COMPONENTS=  gui moc uic
Yes, you need both lines currently. See audio/kid3-kde4 or 
x11-themes/gtk-qt4-engine for examples.

> 2) Is there an easier way to tell which QT4 components are really required
> without looking a every header file in the project?
You may use ldd to find qt4 libraries required by ports binary/libraries, eg:
~> ldd /usr/local/kde4/bin/kid3 |grep -i qt
        libQtSvg.so.4 => /usr/local/lib/qt4/libQtSvg.so.4 (0x28be3000)
        libQtCore.so.4 => /usr/local/lib/qt4/libQtCore.so.4 (0x28cc3000)
        libQtGui.so.4 => /usr/local/lib/qt4/libQtGui.so.4 (0x28ffe000)
        libQtNetwork.so.4 => /usr/local/lib/qt4/libQtNetwork.so.4 (0x2983b000)
        libQtDBus.so.4 => /usr/local/lib/qt4/libQtDBus.so.4 (0x29924000)
        libQtXml.so.4 => /usr/local/lib/qt4/libQtXml.so.4 (0x2997d000)

corresponding qt components (corelib is omitted):
QT_COMPONENTS= svg gui network dbus xml

kde4 ports also need qt tools like qmake, uic. So the full line will be:
QT_COMPONENTS=	svg gui network dbus xml \
		qmake_build moc_build rcc_build uic_build

Sometimes uic3_build and/or porting_build components are required.

Have a nice porting :)


More information about the kde-freebsd mailing list