> On May 12, 2022, at 5:44 AM, Guillaume wrote:
> 
>> 
>> It seems Qt6 (without webkit) is supported, but it will disable printing and 
>> manual. I will try to enable Qt6 builds for Tumbleweed.

Qt6 support is marked 'experimental' for good reasons.

Qt6 doesn't ship with QtWebKit or QtLocation.

Which means no printing, no maps.

That really isn't a useful user experience. Which is why we have a couple of 
test builds that play with this, but absolutely DO NOT RECOMMEND using this as 
end users. So no, please do not suggest Qt6 builds to anyone but developers 
trying to fix the remaining bugs and reworking the printing code to no longer 
require QtWebKit (which is insanely painful because of odd race conditions in 
the way things are rendered in WebEngine).

I have built QtLocation against Qt 6.3 (which has a bunch of bugs, still, and 
is still being rewritten - it's not clear this will even make it into Qt 6.4), 
done some quick hacks for our map plugin, and as I mentioned there are some 
occasional efforts to move printing to a different software stack - but for the 
end user that really is a long, long time away from being useful.

> It currently fails with:
> [   69s] -- Could NOT find Qt6WebKitWidgets (missing: Qt6WebKitWidgets_DIR)
> [   69s] CMake Error at CMakeLists.txt:321 (find_package):
> [   69s]   Found package configuration file:
> [   69s] 
> [   69s]     /usr/lib64/cmake/Qt6/Qt6Config.cmake
> [   69s] 
> [   69s]   but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be 
> NOT
> [   69s]   FOUND.  Reason given by package:
> [   69s] 
> [   69s]   Failed to find Qt component "WebKitWidgets".
> [   69s] 
> [   69s]   Expected Config file at
> [   69s]   "/usr/lib64/cmake/Qt6WebKitWidgets/Qt6WebKitWidgetsConfig.cmake" 
> does NOT
> [   69s]   exist
> 
> Whereas WebKitWidgets should not be used here, since we use Qt6.
> Any idea?

It should set printing to false and therefore not require WebKit, but since 
this is all experimental, this may not have been tested outside of two specific 
implementations (I test the preliminary Qt6 builds on Fedora 35 (without maps) 
and on macOS 12.3)

> Also, the googlemaps part seems to still use qt5.

Googlemaps isn't compatible with Qt6. I have some hacky patches that I use in 
my macOS builds, but those need to be cleaned up before I can send them 
upstream...

/D

_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to