335406 - Fixing the QT build

Status: RESOLVED WONTFIX

(Core Graveyard :: Ports: Qt, defect)

Description

[Ivan Wong]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060313 Debian/1.5.dfsg+1.5.0.1-4 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060313 Debian/1.5.dfsg+1.5.0.1-4 Firefox/1.5.0.1

Any hope that the QT build will resume? Firefox/QT is nice but embedded-moz/qt is really useful IMHO.

Reproducible: Always

Comment 1

[Ivan Wong]

Attachment: first attemp to fix the qt build

This is my first attemp to fix it. I am new to mozilla development so I may have made somethings very wrong. I would like to ask that is it possible and if possible what's the proper way to link to bin/components/libgfx_qt.so from libwidget_qt.so? For now I just blindly add -L../../../dist/bin/component but it sounds evil.

Comment 2

[Philip Withnall (unavailable)]

I don't know much about the QT efforts, but perhaps you would've been best off trying to fix some of the already reported QT bugs? :-P

Comment 3

[Andrew Schultz]

FWIW, trunk is moving to using cairo as the backend graphics engine (compiled with --enable-default-toolkit=cairo-gtk2).  In the not-to-distant future non-cairo bits will be removed, so to get QT going again on the trunk, you'd need to get qt-cairo working and it seems interest in Cairo is low within the QT community

http://dot.kde.org/1135084395/1135100106/

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

no, getting the qt port to work with cairo should be quite easy. all you need to do is initialize cairo's xlib surface with the right data, which can easily be gotten from the qt widget or whatever.

Comment 5

[Stuart Parmenter]

can we just drop qt support?

Comment 6

[J.O. Aho]

I wish we had a working qt support, it fits a lot better into a KDE environment than have gtk2 dependency and in some distros they even force on gnome2 dependency.

We could drop gtk2 support instead, as it prevents the "unix" version of SeaMonkey to have same key-combinations as other operating systems has, it's kind of unprofessional to change key-combinations in a such way as it's been done for "unix" version while all others has kept the original key-combinations.

Comment 7

[DarkMageZ]

IF gtk2 support is dropped. then gnome/xfce/flux/* users would be forced to have QT libraries installed on their systems... so that is not a good solution.
IF you want working QT support, then it is up to you to help write the nessesary patches to help make it work.

IF qt support is dropped, then you'll be upsetting some of the QT/KDE users.

Note that there are some patches to help the QT build @ bug #377134.

Comment 8

[Gordon P. Hemsley [:GPHemsley]]

This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX.

[Mass-change filter: graveyard-wontfix-2014-09-24]

Comment 9

[Kuba Suder]

Oh wow, this was still here? I haven't even used desktop Linux since 2008... :)