latest Windows binary crashes

[Dirk Hohndel]

> On Jul 4, 2017, at 9:19 AM, Thiago Macieira <thiago at macieira.org> wrote:
>> I was told on the Qt list that there is a MUCH newer branch that I should
>> try - they have updated to a current WebKit. The thing that's odd... between
>> 5.7.1 (which the Windows binaries used to be based on) and 5.9 there
>> shouldn't really have been any WebKit changes... so why does it crash now.
> 
> There are a number of minor changes submitted to the 5.8 and 5.9 branches by 
> people like Konstantin, Allan and me. Mine were mostly just to make it, but 
> looking at the diff there appear to be a couple of backports from upstream.

OK. For now I have given up on upgrading the libraries in the Windows
binary. BLE isn't supported, anyway, so whatever. I'll stick with 5.7.1 as
that creates working builds for me.

I'll revisit this when I have an excess of time on my hands :-)

>>> i mean i can possibly find the offending line of code, but i won't
>>> really have a good fix for it. after seeing that unpredictable Marble
>>> multi-threading crash on Windows, i think we are entering the
>>> territory of big, complicated but unmaintained libraries that simply
>>> may not run with the latest Qt version. Qt 6.0 is coming too...
>> 
>> I think they are working on 5.10 ...
> 
> Qt 6.0 will be discussed at the Contributor Summit this year in Berlin. The 
> current idea is that 5.12 will be LTS and then 6.0. That would put 6.0 about 
> two years away from now.

Interesting. Will 6.0 once again be incompatible as the major version bump
implies? What will change?

>>> so we need to:
>>> 1) move away from these unmaintained libraries
>>> WebKit - currently we are stuck with WebKit on Windows
>>> Grantlee - we are stuck with Grantlee due to the template syntax which
>>> the users are already using
>>> Marble - we probably should start using a 2D map of sorts
>> 
>> WebKit - I think we are stuck with that for a while
>> Marble - Tomaz has this working with the latest, maintained Marble
>> Grantee - I have this working on Mac
> 
> What happened to the idea of using QtLocation for maps?

We talked about this here a few times.
We absolutely have to have satellite images. Maps are useless for a dive log.
And QtLocation appears to only support maps. So no go.

I like Lubomir's idea of just using a web browser pointing at an appropriately
customized web page. Let's see where this takes us. We only use Marble on
the desktop, so the restrictions with showing web pages don't bother us.

>>> BTW you can try building this QtWebKit port as it's actively updated:
>>> https://github.com/annulen/webkit/releases
>> 
>> Yes, and that appears to be in the 5.212 branch of Qt that I need to
>> find the time to investigate...
> 
> 5.212 builds with CMake, not qmake anymore. My recommendation is that you 
> build it after all the rest of Qt.

Hmm. I still haven't looked at this. Too many parts of the code that are in
motion, too many platforms, too little help, too little time...

So 5.212 is just QWebKit that I build against an existing Qt build?
Of course, I will still have to build from source for Linux and Android, it seems,
as in both cases 5.9.1 is missing BLE patches from Alex that we need...

/D