On 25/6/19 7:28 pm, Christian Kandeler wrote:
On Mon, 24 Jun 2019 23:25:38 +0000
Hamish Moffatt <ham...@risingsoftware.com> wrote:
On 25/6/19 8:46 am, Thiago Macieira wrote:
On Monday, 24 June 2019 08:24:25 PDT Thiago Macieira wrote:
Anyway, let's stop speculating. Until we can reliably reproduce this problem
to understand what's going on, we're shooting in the dark.
I managed to reproduce this once. It was a left-over .qmake.stash file up in
the directory tree that was telling qmake to use an SDK version that was no
longer installed. I don't know how that file got created...
I also had problems with a stale SDK version in .qmake.stash when I
first upgraded to Qt 5.12. https://bugreports.qt.io/browse/QTBUG-71620
Despite this being entirely qmake's problem it was closed as invalid.
"Out of scope", actually.
My point was that the file is entirely managed by qmake, so (IMHO) qmake
should deal with it if the data is now stale.
Hamish
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
