[Slackbuilds-users] Qt6 libs proposal for SlackBuilds
Ruoh-Shoei LIN
lin.ruohshoei at gmail.com
Tue Oct 28 10:20:24 UTC 2025
Antonio Leal via SlackBuilds-users:
> Qt6 could be better in SlackBuilds.
>
> The fact is some packages just build with older/archived versions of Qt6, others require recent ones and don't build with the former.
>
> Then, within each Qt6 release, there are the extension&submodules, for sure not all required for our current SlackBuilds apps.
>
>
> SlackBuilds should not have just one "Qt6" but several, maybe implementing just the minimum libs required, depending to the apps requirements (at maintainer request)
>
> Location should be something like, for example, /opt/Qt6.4.3 ... /opt/Qt6.9.3 ..etc.
>
>
> Take MuseScore: It is _validated_ against Qt6.9.1 and it needs submodules qtbase, qt5compat, qtnetworkauth, qtscxml, qttools, qtdeclarative and qtsvg, not the whole thing
>
> But 6.9.1 does not fit for example Sigil...
>
> Antonio
>
Regarding Qt version, I have tested 6.10.0, 6.9.3, and 6.8.3.
With gcc 11.2.0 and llvm 20.1.8 (Qt6 needs llvm >=17),
qtrpc could not be built since 6.5.x, there are no pkgs in SBo which
depend on qtrpc, so I disabled the qtrpc module.
QtWebEngine could not be built since 6.9.x, so I stayed on 6.8.x and
would like to retry when Qt 6.10.1 is released.
With gcc 11.2.0 and llvm 13.0.0,
For Qt 6.5.x, qtrpc, qttools, and qdoc could only be built if the Qt
SlackBuild used a workaround, a prebuilt llvm13 binary, then the
compiled version linked to version 13 of the llvm libs available in
stock slackware.
Willy Sudiarto Raharjo:
> Take a look at this on progress on newer Qt6
> https://github.com/SlackBuildsOrg/slackbuilds/pull/12756
>
> it seems that newer qt6 requires newer llvm, which breaks the SBo rule
> unless we added newer llvm into SBo, but that *could potentially* make
> another mess (i might be wrong on this)
>
>
> --
> Willy Sudiarto Raharjo
>
The modules qttool and qdoc of Qt>=6.8 need newer clang, and depend on
newer llvm libs, e.g., libLLVM.so, libclang-cpp.so, libclang.so.
If any other pkgs make use of the newer llvm in compile-time, they
will also need the new libs in runtime.
So I plan to place llvm in /opt/llvm-opt and link the necessary libs
to /usr/lib$LIBDIRSUFFIX.
llvm-opt will need to be specified in every SlackBuild if necessary:
if [ "${LLVM_OPT:-ON}" = "ON" ]; then
export PATH="/opt/llvm-opt/bin:$PATH"
if [ -z "$LD_LIBRARY_PATH" ]; then
export LD_LIBRARY_PATH="/opt/llvm-opt/lib$LIBDIRSUFFIX"
else
export LD_LIBRARY_PATH="/opt/llvm-opt/lib$LIBDIRSUFFIX:$LD_LIBRARY_PATH"
fi
fi
After compiling, the pkg will depend on llvm libs in /usr/lib$LIBDIRSUFFIX
instead of /opt/llvm-opt/lib$LIBDIRSUFFIX.
Christoph Willing:
>
> I believe qt6 has no active maintainer at the moment. Are you volunteering?
>
> If so, remember that building a specialised version with minimum extensions & modules that just suit one of your own pet projects means that it may not be suitable for anything else. A big monster version with everything possible included (like -current?) will be much more useful to SBo users.
>
> chris
>
>
If possible, I would like to build the latest version, of course it will
be the single qt-everywhere-src tarball.
Didier Spaier via SlackBuilds-users:
> Do we need the most recent qt6 for 15.0? Just curious.
>
> Currently in Slint we have llvm 17.0.6, needed by LXQt 2.2.0 (thanks for Frank
> Honolka for the packaging) and a dependency of audacious 4.5.1 and its plugins.
> Note: llvm13-compat from Slackware is used as build dependency of llvm here.
>
> Cheers,
> Didier
>
The latest dolphin-emu, pcsx2 need recent qt6.
Regards,
Lin
More information about the SlackBuilds-users
mailing list