[Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS
patrickkidd at gmail.com
Tue Jul 2 21:41:30 CEST 2019
`rm -rf` on your build does not solve this issue because the .qmake.stash
file often exists in a path above the build/source dir.
On Wed, Jun 26, 2019 at 5:23 PM Thiago Macieira <thiago.macieira at intel.com>
> On Wednesday, 26 June 2019 16:22:48 PDT Hamish Moffatt wrote:
> > My point was that the file is entirely managed by qmake, so (IMHO) qmake
> > should deal with it if the data is now stale.
> It's very difficult to do that. The whole reason the file exists is to
> having to call the compiler to find out its details every time that qmake
> started. In order to do what you are asking for, we need to call out to
> compiler, which defeats the purpose.
> Also, changing the compiler does require erasing your build and starting
> anyway. For example, if you're using precompiled headers, a version update
> the compiler (even patch level) can invalidate those files and neither
> nor Make will notice that.
> My point is that this is a bigger problem than just the .qmake.stash file.
> really recommend just rm -rf your build.
> PS: make your life easier and don't configure Qt from inside the sources.
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel System Software Products
> Interest mailing list
> Interest at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest