Package Details: lib32-qt4 4.8.7-15

Git Clone URL: https://aur.archlinux.org/lib32-qt4.git (read-only, click to copy)
Package Base: lib32-qt4
Description: A cross-platform application and UI framework (32-bit)
Upstream URL: http://www.qt.io
Licenses: custom, GPL3, LGPL, FDL
Conflicts: lib32-qt
Replaces: lib32-qt
Submitter: arojas
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 51
Popularity: 0.000000
First Submitted: 2017-02-09 20:36 (UTC)
Last Updated: 2019-11-19 22:10 (UTC)

Pinned Comments

WoefulDerelict commented on 2017-03-07 19:07 (UTC) (edited on 2018-08-26 01:22 (UTC) by WoefulDerelict)

This package often requires special care to build. If building this with makepkg fails it will be necessary to construct the package in a clean chroot. Using an AUR helper is not recommended; however, aurutils does provide the option to build in the clean chroot.

The process of building this package in a clean chroot is rendered exceptionally simple with the help of scripts in the devtools package and can be completed via the following steps. These summarize the information provided by the Arch Linux DeveloperWiki and assume familiarity with git or the process of downloading a snapshot from the AUR and extracting the archive. Please refer to this article for more information about the devtools scripts and building in the clean chroot: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot]

Prerequisites: This process uses scripts in devtools to simplify the procedure: please install this package before beginning. The lib32-libmng package is required and must be built or downloaded from the Arch Linux Archive [https://wiki.archlinux.org/index.php/Arch_Linux_Archive]. QT 4 depends on this package and it is no longer found in the binary repositories.

  1. Clone the lib32-qt4 repository or extract the snapshot archive into a clean working directory.

  2. Enter the directory containing the package source. (PKGBUILD and patches.)

  3. Execute the following command, supplying the location of lib32-libmng: multilib-build -- -I /<somewhere>/lib32-libmng-2.0.3-1-x86_64.pkg.tar.xz

  4. Execute pacman with the -U flag to install the resulting package: just as one would with any other local package. Note: lib32-libmng would need to be installed in a similar fashion if it isn't already present on your system.

WoefulDerelict commented on 2017-02-25 15:52 (UTC) (edited on 2018-08-26 00:47 (UTC) by WoefulDerelict)

The QT 4 build system is prone to some odd behaviour: especially if the qtwebkit package is installed. [https://bbs.archlinux.org/viewtopic.php?id=132416] [https://bugreports.qt.io/browse/QTBUG-20236]

If your build fails with the following [error: expected class-name before ‘{’ token] when compiling please build in a clean chroot.

If your build fails with error messages about skipping incompatible files and being unable to find a specific file in a compatible format, especially while linking, you will need to build in a clean container to avoid issues.

Building this package in a clean chroot or other form of container will prevent unexpected issues.

All build errors will be ignored unless the build was performed inside a clean, properly configured container. For more information about building in a clean chroot see this article: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot]

Big thanks to int [at] arcor [dot] de for doing the legwork to track down the relevant issue reports and sending them my way.

The archlinuxgr repository contains a binary copy of this package courtesy of ranger.

[archlinuxgr] Server = http://archlinuxgr.tiven.org/archlinux/$arch

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 25 Next › Last »

PhotonX commented on 2017-03-01 21:47 (UTC) (edited on 2017-03-01 21:48 (UTC) by PhotonX)

Thanks for the quick reply, guys! Before the update it looked like this (the variant "Use desktop settings" is selected in the "Style" settings): http://imgur.com/8SJe0uX Now it looks like this: http://imgur.com/ipZLvJo I can make it look the way it looks on you screenshot, @ranger, by selecting "Cleanlooks" in the "Style" settings, but this is still worse than what it was before the update, where it really integrated with the GTK2 theme being used (see my first screenshot).

ranger commented on 2017-03-01 20:56 (UTC) (edited on 2017-03-01 21:39 (UTC) by ranger)

which version of skype are you using? I use the latest stable and my skype looks like that http://imgbox.com/oLwPXqxr

WoefulDerelict commented on 2017-03-01 20:43 (UTC)

PhotonX: Yes, to the best of my knowledge ranger used the current version of the PKGBUILD here to build the binary at [archlinuxgr]. There are changes in the locations of some files between -7 and -8 that could be affecting dowstream applications. One would suggest rebuilding the Skype package after updating to see if that has any effect. This isn't something I can test or reproduce.

ranger commented on 2017-03-01 20:36 (UTC)

@PhotonX no problem with skype here

PhotonX commented on 2017-03-01 20:29 (UTC)

Is this PKGBUILD the base of the binary package in archlinuxgr/? If so: After the update to -8 (in archlinuxgr/), Skype falls back to a pre-2000 looking ugly theme. Downgrading to -7 solves the problem. Any thoughts?

WoefulDerelict commented on 2017-02-25 15:52 (UTC) (edited on 2018-08-26 00:47 (UTC) by WoefulDerelict)

The QT 4 build system is prone to some odd behaviour: especially if the qtwebkit package is installed. [https://bbs.archlinux.org/viewtopic.php?id=132416] [https://bugreports.qt.io/browse/QTBUG-20236]

If your build fails with the following [error: expected class-name before ‘{’ token] when compiling please build in a clean chroot.

If your build fails with error messages about skipping incompatible files and being unable to find a specific file in a compatible format, especially while linking, you will need to build in a clean container to avoid issues.

Building this package in a clean chroot or other form of container will prevent unexpected issues.

All build errors will be ignored unless the build was performed inside a clean, properly configured container. For more information about building in a clean chroot see this article: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot]

Big thanks to int [at] arcor [dot] de for doing the legwork to track down the relevant issue reports and sending them my way.

The archlinuxgr repository contains a binary copy of this package courtesy of ranger.

[archlinuxgr] Server = http://archlinuxgr.tiven.org/archlinux/$arch

WoefulDerelict commented on 2017-02-25 15:33 (UTC)

tc1384: It is probably much easier to use mesa to provide libgl instead of nvidia inside a container. If one recalls correctly you'll have to enable [Multilib] inside the container before attempting to fetch the lib32- dependencies. Obviously this process eats a sizeable chunk of disk space for the container.

ranger commented on 2017-02-25 15:05 (UTC)

denixx, I uploaded a package but my comment is lost somewhere near the bottom :p you can find the package here [archlinuxgr] SigLevel = PackageOptional Server = http://archlinuxgr.tiven.org/archlinux/$arch

denixx commented on 2017-02-25 14:53 (UTC)

Eh. This package is kind of time waster. Can it be precompiled to binaries? It builds a couple of hours. :)

tc1384 commented on 2017-02-25 08:35 (UTC)

I tried building in a clean chroot but have been unable to resolve lib32-nvidia-libgl dependencies.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 25 Next › Last »