On 2022-10-02 20:07, Kevin Kofler via devel wrote:
Hi,
with the wxWidgets 3.2.0 release, there is now finally a wxQt backend
available. Are there any plans yet to package that?
I don't have any current plans to package it. Though the wxQt port
exists, as far as I can see, it isn't as well maintained at the wxGTK
(and Windows/macOS) ports.
Currently, the Fedora wxWidgets package (even the specfile and SRPM) is
called wxGTK, even though it is actually built from the generic
wxWidgets
tarball. Can we not build the different backends from the same SRPM?
Then we
should rename the source package to wxWidgets and build both wxGTK and
wxQt
from it.
Indeed, the wxGTK package is poorly named. Yes, it ought to be possible
to build wxGTK and wxQt from the same spec.
And as I understand it, wxWidgets backends cannot be swapped at
runtime, but
applications need to be recompiled to use wxQt instead of wxGTK, is
that
correct? So should we ship all wxWidgets applications in the form of
multiple subpackages compiled against the different wxWidgets backends?
My question would be: has anyone tested the wxQt port, does it work
well, and is there any demand for using it? Otherwise, I don't see much
point in packaging it.
Scott
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
