Supported linuxes



  • From what I see, Qt problems that others have and I have encountered have to do, not with Qt code design, but with issues surrounding installation and configuration.

    As a beginner in Qt, I find that this is where I experienced a definite shortcoming.

    Now I am reading about 5.0 version, and from what is posted, the only supported linux listed is Ubuntu. My experience with Qt is that since Ubuntu switched to Unity, there are problems with Qt startup (initialization) code. May I suggest strongly that we need Qt to support Debian's successors and Red-Hat / SUSe successors (yum rpm).

    The code that would not work well with UBUNTU 10.43 and 11.10 ran flawlessly with Fedora, with Linux Mint12, and with Debian as well as Scientific Linux (Centos), both with 32bit and 64bit.
    There is something not correct in the Ubuntu GUI interfaces.

    May I suggest a set of teams be setup to use a given test suite, and that they confirm the functionality of this test suite on target platforms such as Centos, Ubuntu, Fedora/RedHat, Intel, Archlinux, Suse, and whatever other version rises to popularity. I will be glad to undertake verifying successful execution of a test suite validation for Fedora 32bit and for Fedora 64bit.



  • Hi

    first of all, please don't do necroposting, especially, if the topic you have is totally independant of the original one (the original one was about embedded stuff, not desktop).

    Second: who says, other linuxes will not be supported?



  • [quote author="lsatenstein" date="1323985199"]
    The code that would not work well with UBUNTU 10.43 and 11.10 ran flawlessly with Fedora, with Linux Mint12, and with Debian as well as Scientific Linux (Centos), both with 32bit and 64bit.
    There is something not correct in the Ubuntu GUI interfaces.
    [/quote]

    ...or with Ubuntu at all. I don't believe Qt is in a position to force a Linux vendor to adopt the library for its GUI.
    Moreover, while it is really important to have a good level of support on all the operating system (are we still writing cross platform applications?), I don't care if one Linux requires a more detailed configuration or custom installation in order to use Qt. It is simply impossible to deal with all distros.

    [quote author="lsatenstein" date="1323985199"]
    May I suggest a set of teams be setup to use a given test suite, and that they confirm the functionality of this test suite on target platforms such as Centos, Ubuntu, Fedora/RedHat, Intel, Archlinux, Suse, and whatever other version rises to popularity. I will be glad to undertake verifying successful execution of a test suite validation for Fedora 32bit and for Fedora 64bit. [/quote]

    Glad to hear you can help. Have you already took a look "here":http://developer.qt.nokia.com/contribute?



  • I'm using Qt SDK without problems with my Slacware Linux 13.37 and I didn't have problems with all previous Slackware version.

    The only problem I encountered was with gdb and "debugger helper" but I "solved":http://developer.qt.nokia.com/forums/viewthread/7525/ it...



  • I use Qt SDK in Open Suse 11.3 with no problems.

    I think that what you propose is a waste of time.

    Cheers!



  • Ubuntu is a Tier 1 platform, which means that it is used for testing etc. Qt is supposed to work on all modern Linux flavors. Be aware that the Qt version provided by the different venders are often modified and patched. So, to see whether it's a Qt problem or one of the distribution, you should check your application against a vanilla build of Qt, most probably built manually.



  • lsatenstein wrote:
    "The code that would not work well with UBUNTU 10.43 and 11.10 ran flawlessly with Fedora, [...] "

    I am interested in using the latest Qt. With Linux
    Fedora, there is the "make install" command (for root)
    to install "system-wide": this, I don't wish to use,
    so as not to disturb any Qt packages from Fedora 16.

    So, can I download a .targz archive, to my home
    directory, and then run say: ./configure
    then `make' , to get a Qt executable, documention,
    etc. only in my home folder, /home/david/ , say
    a sub-folder: /home/david/SandboxQt/ ?

    UPDATE: I now have Qt SDK installed in a sub-directory of
    my Home directory in Linux Fedora 16 .
    No problems so far ...

    The point of this is not to disturb system settings
    for my Fedora install ...

    I can explain more; also, I would be interested
    in pointers to documentation about installing/making
    from source code, as with GNU Make, etc.

    Thanks.



  • You can give the -prefix parameter to the configure script of the Qt sources. make install will install everything in that directory and nowhere else.

    PS:
    http://developer.qt.nokia.com/doc/qt-4.8/installation.html



  • OK, I apologize for not necessarily posting to the appropriate area. I have an application that is purely keyboard oriented. With all distributions except one, the keyboard worked flawlessly. With that one, it took a mouse click event to unblock keyboard use. I tested with 32bit and 64bit Linux versions mentioned in an earlier posting.

    The Qt mouse events worked flawlessly, but not the keyboard ones on two systems. (both derived from a common base system. On that base system, Qt worked just fine.

    Was it my code, or the host linux? Since my code worked on other Linux versions from the onset, my conclusion is/was that there is perhaps a QT initialization problem. The major Qt function was based on the QtTableWidget object. (may have misspelled object name).

    Sure, I would like to help with testing and documentation.



  • I can give you example that some parts of system can make issues in your application. In KDE you can use a Oxygene theme - it looks good but application has another feature if you use this theme. Oxygene has a feature "drag by empty spaces", so your app will be draggable by emty spaces until you disable this feature in oxygene-settings. Maybe you have on ubuntu something that change an events in your app?


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.