This forum has been archived. All content is frozen. Please use KDE Discuss instead.
The Discussions and Opinions forum is a place for open discussion regarding everything related to KDE, within the boundaries of KDE Code of Conduct. If you have a question or need a solution for a KDE problem, please post in the apppropriate forum instead.

KDE SC and it's gtk dependencies

Tags: None
(comma "," separated)
Amnon82
Registered Member
Posts
3
Karma
0
OS

KDE SC and it's gtk dependencies

Thu Jun 17, 2010 12:02 am
Is it possible to create a working KDE-Desktop without any gtk-dependency?

I know that KDE SC is qt-based. Some apps like phonon, koffice and even qt might need gtk too to work properly or even build. gtk is only needed for gtkstyle in qt and that is only needed to display qt-based apps in Gnome native gtkish.

A standard linux desktop must have both installed: qt and gtk to work as expected. So what might happen when you remove all gtkish things from your repos? Is it still possible to have a working KDE SC?

Also how can you get all needed deps for KDE SC? Checking tarball by tarball or is there a list of all needed stuff?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
If the Gtk development headers are not installed when Qt is compiled, then GtkStyle support will be automatically removed from the build. Note that this will also remove support for iPod's from Amarok, as it is used to handle album art among other things.

As far as I am aware though, no component of KDE has a hard dependency upon Gtk.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
bcooksley is right. In historical times, people confused GLib support (which is required by some bits of KDE) with GTK+ dependencies, while they aren't the same thing.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
jglen490
Registered Member
Posts
77
Karma
1
OS

Re: KDE SC and it's gtk dependencies

Thu Jun 17, 2010 12:58 pm
What, in your mind, is the difference between a "hard" dependency and any other kind of dependency.


I feel more like I do now than I did when I got here.
Proudly wearing a negative Karma.
Kubuntu 12.04 .2, Dell Dimension 3000
User avatar
anda_skoa
KDE Developer
Posts
783
Karma
4
OS
A hard or mandatory dependency is usually something you cannot build without, while an optional dependency is something you can build without but will get certain features deactivated.

E.g. no Qt -> No KDE, No Google Widget SDK -> No support for Google Desktop widgets on the Plasma Desktop.


anda_skoa, proud to be a member of KDE forums since 2008-Oct.
jglen490
Registered Member
Posts
77
Karma
1
OS
O.K., thank you. Hadn't heard of a distinction before; tailoring, yes, distinction, no.


I feel more like I do now than I did when I got here.
Proudly wearing a negative Karma.
Kubuntu 12.04 .2, Dell Dimension 3000


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot]