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

logan.massey

@ChrisW67 said in Cannot build QtWayland plugin when building qt from source for 32bit.:

@logan-massey said in Cannot build QtWayland plugin when building qt from source for 32bit.:

To build the QtWayland module you need the external dependencies:
xkbcommon - http://xkbcommon.org/
wayland - http://wayland.freedesktop.org/

I have seen this and used apt install to try and get any and everything related to wayland and xkbcommon. But seeing it now I realize that it is something I need to go grab from the website. I have downloaded these and am reconfiguring now. I will let you know if this solves my issue.

> What did you think were the correct dependencies?
I have used apt install to download any wayland or xcb/xkb library available. I believe I understand the error of my mistake relevant to dependencies now.

> What did you actually install into your Ubuntu VM?
I am using a VirtualBox vm with an Ubuntu .iso

> What virtual display hardware is present?
I am using a laptop with 2 additional monitors

> How did you build Qt? What version?
I built qt by following this guide. Qt version 6.9

logan.massey

@Durugesha

@Durugesha said in Cannot build QtWayland plugin when building qt from source for 32bit.:

> sudo apt-get install build-essential libgl1-mesa-dev
These have already been downloaded

> example - ../configure -prefix pathtoinstall -xcb -xcb-xlib -bundled-xcb-xinput -developer-build -wayland -- -DQT_BUILD_TESTS_BY_DEFAULT=OFF
Previously using any of these flags (-xcb, -xcb-xlib, etc...) have resulted in errors mentioning something along the lines of "Forcing XCB to ON breaks its state". But I have followed @ChrisW67 suggestions in the post above and believe this may be my issue. I will try to build without these flags, then if I still run into issues I will add these flags and report my results here.

Thank you for your reply.

SGaist

Hi,

Unrelated to your issue, unless you plan to hack on Qt itself, drop the -developer-build option.

logan.massey

@SGaist said in Cannot build QtWayland plugin when building qt from source for 32bit.:

Hi,

Unrelated to your issue, unless you plan to hack on Qt itself, drop the -developer-build option.

the man, the myth, the legend, @SGaist

I'm currently building with that option enabled. Does it alter qt in any major way? Or is it fine to use a build that has that option?

SGaist

@logan-massey it modifies some of the flags used for the build (sorry I don't remember the details right now). The point is that the build is not optimized as a release build which is what you want to have for building and distributing your applications.

logan.massey

@SGaist okay will reconfigure without it, thank you.

logan.massey

@Durugesha @ChrisW67 So currently while trying to configure with these flags "-xcb, -xcb-xlib, -bundled-xcb-xinput", I get the following 2 errors:

I also figure this would be relevant, what can I do to ensure these (xkbxommon-x11,, and xcb-sm) are "yes" ?

When in fact i have this installed already

Also, qtwayland says it is still missing required dependencies:

Thank you for your help!

SGaist

Hi,

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

logan.massey

@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:

SGaist

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

logan.massey

@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

The configure output throws this warning:

When I go to that file and look at line 26, I see this conditional:

I can confirm I have WaylandScanner:

And this shows I am using Wayland:

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:

After running the configure script again with this new CMakeLists.txt file, I see this:

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.

SGaist

Do you have the wayland development libraries installed ?

logan.massey

@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

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.

logan.massey

@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:

before it failed, it spit out these warnings:

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.

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.

logan.massey

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