Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Cannot build QtWayland plugin when building qt from source for 32bit.
Forum Updated to NodeBB v4.3 + New Features

Cannot build QtWayland plugin when building qt from source for 32bit.

Scheduled Pinned Locked Moved Unsolved General and Desktop
20 Posts 4 Posters 1.8k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • DurugeshaD Durugesha

    Hello @logan-massey,
    you are getting this two error because your Qt source code build is not generated xcb and wayland flatform libraries.

    sudo apt-get install build-essential libgl1-mesa-dev
    try the above common for build essentials. in configure commond add both wayland and xcb.
    example - ../configure -prefix pathtoinstall -xcb -xcb-xlib -bundled-xcb-xinput -developer-build -wayland -- -DQT_BUILD_TESTS_BY_DEFAULT=OFF

    L Offline
    L Offline
    logan.massey
    wrote on last edited by logan.massey
    #10

    @Durugesha @ChrisW67 So currently while trying to configure with these flags "-xcb, -xcb-xlib, -bundled-xcb-xinput", I get the following 2 errors:
    35e046f9-85f0-4f6e-bd0c-4572f51bef72-image.png

    I also figure this would be relevant, what can I do to ensure these (xkbxommon-x11,, and xcb-sm) are "yes" ?
    7c0915b2-051a-4dff-915e-6e0aaa736c5b-image.png

    When in fact i have this installed already
    651a931b-7343-41db-b72f-78a684b22ea0-image.png

    Also, qtwayland says it is still missing required dependencies:
    fdf04ad7-b151-4979-b3ef-cd61dfd89b24-image.png

    Thank you for your help!

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #11

      Hi,

      Did you restart the configuration from a clean state after installing the missing dependencies ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      L 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        Did you restart the configuration from a clean state after installing the missing dependencies ?

        L Offline
        L Offline
        logan.massey
        wrote on last edited by logan.massey
        #12

        @SGaist

        I delete all folders in the build folder. And start a new terminal. Is that enough?

        Once I removed the -developer-build option from the configure line, like you suggested earlier, I started getting those "Forcing to ON breaks its condition" errors, so I am only using the -bundled-xcb-xinput option.

        Also, I am skipping a good amount of modules to keep the space it takes up fairly low and since I have encountered errors building all of them in the past. Here is a screenshot of my full configure line:
        9f453d65-1be3-499a-8adf-8eeb264e60f1-image.png

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #13

          Check the logs generated from the configure tests, they might give you more hints about what is going wrong.

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          L 1 Reply Last reply
          0
          • SGaistS SGaist

            Check the logs generated from the configure tests, they might give you more hints about what is going wrong.

            L Offline
            L Offline
            logan.massey
            wrote on last edited by logan.massey
            #14

            @SGaist
            After a break from this, I am back and retrying. This is where I stand now. Help would be much appreciated as I am a little naive with this topic. Thanks

            I do not see any log files. Only file i see is the config.summary file. Which only mentions wayland once
            3c667f4f-0810-41b6-9359-c3c0bf2afcae-image.png

            The configure output throws this warning:
            66833ead-815e-4f1a-b5ac-f5f9bf3d1bbc-image.png

            When I go to that file and look at line 26, I see this conditional:
            1bac9130-b3f2-406e-b1ee-08b624d77ba0-image.png

            I can confirm I have WaylandScanner:
            9875128c-4d76-43e0-b7e0-8789a1e42a2b-image.png

            And this shows I am using Wayland:
            f852c5d8-1236-47a2-8a3b-1d63055e86c8-image.png

            So to figure out which conditional was failing, I modified the CMakeLists.txt in the wayland/src folder by splitting the conditional into two if statements:
            ce48d163-db6b-4e2d-bcd9-4ac8bd50ac40-image.png

            After running the configure script again with this new CMakeLists.txt file, I see this:
            f63df84d-dde2-4805-8215-11704814fcde-image.png

            This tells me that the NOT Wayland_FOUND conditional is what is throwing this. I'm not positive what this means since I am running Wayland already since it comes with Ubuntu pre-installed.

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #15

              Do you have the wayland development libraries installed ?

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              L 1 Reply Last reply
              0
              • SGaistS SGaist

                Do you have the wayland development libraries installed ?

                L Offline
                L Offline
                logan.massey
                wrote on last edited by
                #16

                @SGaist

                The Wayland Development libraries I already have installed are as follows:

                libwayland-dev
                libffi-dev
                libwayland-bin
                libwayland-client0
                libwayland-cursor0
                libwayland-egl1
                libwayland-server0
                libwayland-doc

                1 Reply Last reply
                0
                • SGaistS Offline
                  SGaistS Offline
                  SGaist
                  Lifetime Qt Champion
                  wrote on last edited by
                  #17

                  I just saw that the cmake file looks for 1.15 and you have wayland 1.20. I wonder if it comes to that.

                  Interested in AI ? www.idiap.ch
                  Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                  L 1 Reply Last reply
                  0
                  • SGaistS SGaist

                    I just saw that the cmake file looks for 1.15 and you have wayland 1.20. I wonder if it comes to that.

                    L Offline
                    L Offline
                    logan.massey
                    wrote on last edited by
                    #18

                    @SGaist
                    spent yesterday working on this suggestion. Got wayland1.15 built and installed.

                    I ran the configure script for qt and didnt see any issues with configuring the qtwayland module. Started building and it failed with this error:
                    b292b078-0f03-432f-9426-eeab6bbdb889-image.png

                    before it failed, it spit out these warnings:
                    03e90e7f-5e7e-4ef4-ac53-fde048d6dc95-image.png

                    I was trying to open a log file to see if it would give me any more info, but it wasnt opening. So I restarted my VM, and now I get a blinking cursor on a black screen. I feel the issue may be that my version of ubuntu is incompatible with wayland 1.15. Trying to see what I can do to save this machine.

                    1 Reply Last reply
                    0
                    • SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #19

                      As a first step, I would have adapted the script to the version of wayland installed and not replace any system components like that.

                      What you can do is switch to one of the virtual terminal and force reinstall wayland.

                      Another possibility is to ssh into the system.

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      L 1 Reply Last reply
                      0
                      • SGaistS SGaist

                        As a first step, I would have adapted the script to the version of wayland installed and not replace any system components like that.

                        What you can do is switch to one of the virtual terminal and force reinstall wayland.

                        Another possibility is to ssh into the system.

                        L Offline
                        L Offline
                        logan.massey
                        wrote on last edited by
                        #20

                        @SGaist
                        Im back where I was and have fixed the script. Its currently building. Will update with progress

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved