recent build; symbol lookup error in

Lubomir I. Ivanov neolit123 at
Fri May 11 09:40:08 PDT 2018

On 11 May 2018 at 17:30, Dirk Hohndel <dirk at> wrote:
>> On May 11, 2018, at 5:07 AM, Lubomir I. Ivanov <neolit123 at> wrote:
>> On 11 May 2018 at 15:01, Cristian Ionescu-Idbohrn
>> <cristian.ionescu-idbohrn at> wrote:
>>> On Fri, 11 May 2018, Lubomir I. Ivanov wrote:
>>>> Christian, did you try deleting the build folder (including the
>>>> gmaps plugin) completely if you recently updated to a new Qt before
>>>> rebuilding?
>>> Yes, that did the trick, but shouldn't that be detected and rebuilt?
>> CMake probably struggles with the detection of such changes.
>> safest bet is to clean the build dir manually.
> We don't use cmake rules to trigger re-builds of dependencies.
> The idea is that "unless you know what you are doing, please
> start from a clean build using the build script".

i think the script to download the private headers for QtLocation
doesn't handle sudden Qt version changes in regard to the already
present objects code in the build folder.
that aside, it's possible to get other build problems after bumping Qt
so the clean build is really the way to go.


More information about the subsurface mailing list