From: Boris Kolpackov <boris@codesynthesis.com>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>
Subject: Qt6 port of kconfig qconf
Date: Mon, 17 Jul 2023 11:27:16 +0200 [thread overview]
Message-ID: <boris.20230717111132@codesynthesis.com> (raw)
Is there interest in the Qt6 port of qconf (which is currently Qt5)?
I took an exploratory stab at it and I've managed to make it compile
and run with relatively few changes, though there are quite a few
warnings about using deprecated stuff.
I can see three possible approaches here:
1. Drop Qt5 support and port qconf to be exclusively Qt6. This should
allow cleaning up all the deprecated stuff.
2. Support Qt5 and Qt6 in the same qconf.cc. With this approach it's
unlikely we will be able to cleanup the deprecated stuff without
turning it into an #if soup.
3. Leave qconf.cc to be Qt5-only and make the changes in the qconf6.cc
copy. This will allow us to clean up all the deprecated stuff but
will require applying further changes to two files until we drop
support for Qt5.
Thoughts?
next reply other threads:[~2023-07-17 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 9:27 Boris Kolpackov [this message]
2023-07-18 0:33 ` Qt6 port of kconfig qconf Masahiro Yamada
2023-07-18 4:13 ` Boris Kolpackov
2023-07-21 6:37 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=boris.20230717111132@codesynthesis.com \
--to=boris@codesynthesis.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox