[arch-multilib] gtk-theme-engines, libqtcurve request
I have a feature request for the multilib repo for at least lib32-qtcurve or better complete gtk-theme support for a better look of 32 bit gtk-apps on kde4. I do post here as advised by a comment on http://bugs.archlinux.org/task/18687 I hope this is correct. Harvey -- Linux is like a wigwam: No Gates, no Windows and an Apache inside
Am 02.09.2010 10:49, schrieb Harvey:
I have a feature request for the multilib repo for at least lib32-qtcurve or better complete gtk-theme support for a better look of 32 bit gtk-apps on kde4.
The problem is, it seems that qtcurve-kde4 needs at least kdelibs to build - and kdelibs has lots of dependencies. If we can strip kdelibs down to only include the necessary libraries/dependencies for theme engine support, then we can do it, but I'd like to see PKGBUILDs and dependency trees first before we do anything. One of the goals of multilib is to keep the lib32 package set as small as possible. I use qtcurve myself - but if the required number of dependencies is too big, then I'd prefer not having a nice theme over adding all of them.
On Thu, 02 Sep 2010 11:03:28 +0200, Thomas Bächler <thomas@archlinux.org> wrote:
Am 02.09.2010 10:49, schrieb Harvey:
I have a feature request for the multilib repo for at least lib32-qtcurve or better complete gtk-theme support for a better look of 32 bit gtk-apps on kde4.
The problem is, it seems that qtcurve-kde4 needs at least kdelibs to build - and kdelibs has lots of dependencies. If we can strip kdelibs down to only include the necessary libraries/dependencies for theme engine support, then we can do it, but I'd like to see PKGBUILDs and dependency trees first before we do anything.
One of the goals of multilib is to keep the lib32 package set as small as possible. I use qtcurve myself - but if the required number of dependencies is too big, then I'd prefer not having a nice theme over adding all of them.
Afaik qtcurve can be build without kde support. (You wont need it anyway) And the gtk version doesn't need qt or kde at all. -- Pierre Schmitz, https://users.archlinux.de/~pierre
Am 02.09.2010 11:22, schrieb Pierre Schmitz:
The problem is, it seems that qtcurve-kde4 needs at least kdelibs to build - and kdelibs has lots of dependencies. If we can strip kdelibs down to only include the necessary libraries/dependencies for theme engine support, then we can do it, but I'd like to see PKGBUILDs and dependency trees first before we do anything.
Afaik qtcurve can be build without kde support. (You wont need it anyway) And the gtk version doesn't need qt or kde at all.
That would be good news. We have 'qt' anyway, so if that suffices to build it, we can certainly do it. Who wants to write the PKGBUILD?
Am 02.09.2010 11:25, schrieb Thomas Bächler:
Am 02.09.2010 11:22, schrieb Pierre Schmitz:
The problem is, it seems that qtcurve-kde4 needs at least kdelibs to build - and kdelibs has lots of dependencies. If we can strip kdelibs down to only include the necessary libraries/dependencies for theme engine support, then we can do it, but I'd like to see PKGBUILDs and dependency trees first before we do anything.
Afaik qtcurve can be build without kde support. (You wont need it anyway) And the gtk version doesn't need qt or kde at all.
That would be good news. We have 'qt' anyway, so if that suffices to build it, we can certainly do it. Who wants to write the PKGBUILD?
I have no time to make the PKGBUILD right now, but the following configure command seems to work for qtcurve-kde4: CFLAGS="-m32 $CFLAGS" CXXFLAGS="-m32 $CXXFLAGS" LDFLAGS="-m32 $LDFLAGS" PKG_CONFIG_PATH=/usr/lib32/pkgconfig cmake ../ -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DQTC_QT_ONLY=true The installation directory is probably still wrong, but it builds a 32 bit qtcurve.so.
The following PKGBUILD compiles, but skype doesn't seem to pick up the theme. It also doesn't complain about the lack of qtcurve when I uninstall it.
Thomas,
# $Id: $ # Maintainer: Andrea Scarpino<andrea@archlinux.org> # Contributor: Pierre Schmitz<pierre@archlinux.de>
pkgname=lib32-qtcurve-qt4 pkgver=1.5.2 pkgrel=1 arch=('x86_64') license=('GPL') pkgdesc='A configurable set of widget styles for KDE and Gtk (32 bit)' url='http://www.kde-look.org/content/show.php?content=40492' depends=('lib32-qt') makedepends=('cmake' 'automoc4' 'gcc-multilib') source=("http://craigd.wikispaces.com/file/view/QtCurve-KDE4-${pkgver}.tar.bz2") md5sums=('6fc73762101a91a09b1359eb5b2689aa')
build() { export CFLAGS="-m32 $CFLAGS" export CXXFLAGS="-m32 $CXXFLAGS" export LDFLAGS="-m32 $LDFLAGS" export PKG_CONFIG_PATH=/usr/lib32/pkgconfig cd $srcdir mkdir build cd build cmake ../QtCurve-KDE4-${pkgver} \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX=/usr \ -DQTC_QT_ONLY=true \ -DQT_PLUGINS_DIR=/usr/lib32/qt/plugins make }
package() { cd $srcdir/build make DESTDIR=$pkgdir install }
It builds for me too but the app I try to run throws the following error: (Lin-HaBu.app:6749): Gtk-WARNING **: Im Modulpfad »qtcurve« konnte keine Themen-Engine gefunden werden Seems the file is in the wrong path? Harvey -- Linux is like a wigwam: No Gates, no Windows and an Apache inside
Am 02.09.2010 14:52, schrieb Harvey:
It builds for me too but the app I try to run throws the following error: (Lin-HaBu.app:6749): Gtk-WARNING **: Im Modulpfad »qtcurve« konnte keine Themen-Engine gefunden werden
Seems the file is in the wrong path?
Harvey
The package I posted is only qtcurve-qt4 (which is a lib32 replacement for the qtcurve-kde4 package). For GTK applications, you'll need lib32-qtcurve-gtk2, which we can also probably build.
Thomas Bächler <thomas@archlinux.org> wrote:
The following PKGBUILD compiles, but skype doesn't seem to pick up the theme. It also doesn't complain about the lack of qtcurve when I uninstall it.
How is the configuration done? Maybe it looks for Qt config files while the usual package looks for KDE config files ?
Am 02.09.2010 15:02, schrieb Rémy Oudompheng:
Thomas Bächler <thomas@archlinux.org> wrote:
The following PKGBUILD compiles, but skype doesn't seem to pick up the theme. It also doesn't complain about the lack of qtcurve when I uninstall it.
How is the configuration done? Maybe it looks for Qt config files while the usual package looks for KDE config files ?
The configuration dialog creates .config/qtcurve, which seems KDE-independent. I think the somehow lib32-qt doesn't know that it should use qtcurve, I had yet to find out how this is supposed to work.
participants (4)
-
Harvey
-
Pierre Schmitz
-
Rémy Oudompheng
-
Thomas Bächler