-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wayland: Link to Wayland and include Qt private platform headers #218
Comments
Re: default to not enabled. It is not my call, but I admit that for purposes of certain packaging automation that I prefer that configure default to enabled for useful features with the option to disable on the configure command line and a test in configure that disables the functionality if the required headers are not available with a line in the configure results summary reporting the results. Similar to how the recent vulkan option/tests were added to configure. And, at least with the current project CI buildbot configuration, it is likely to get better build coverage as configure does not (currently) use enable overrides (except for symbol-visibility). I suspect that the annoying part will be determining what the various distros name the package with the private headers to add them to the appropriate ansible stanza(s) and test those. |
The longer term intention is to enable by default. Just being cautious in the short term. |
This is complete with the exception of handling Qt private header detection in configure - which I can't figure out yet - so leaving the default behavior to not enabled. |
Qt does not directly expose either the wl_compositor or wl_surface objects to clients. We need these if we are going to call Wayland api's for additional functionality.
Proposal:-
Refs #210 and #216
The text was updated successfully, but these errors were encountered: