Qt 5.8 can't compile, jom errors

[km2442]

Hello, After updating Qt to 5.8 from 5.7 I can't recompile my solution.
There are probems with jom, compiler throws some exceptions:

:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/ATLMFC/INCLUDE/atlbase.(3210): Parse error at "__identifier"
jom: <path>\build-<solution>-Desktop_Qt_5_8_0_MSVC2015_32bit-Release\Makefile.Release [release\moc_mainwindow.cpp] Error 1
jom: <path>\build-<solution>-Desktop_Qt_5_8_0_MSVC2015_32bit-Release\Makefile [release] Error 2
11:56:22: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2.
Error while building/deploying project <solution> (kit: Desktop Qt 5.8.0 MSVC2015 32bit)
When executing step "Make"

On Qt 5.7 everything was Ok. I tried to reinstall VS2015 and Qt, temporary change jom to nmake, but no changes :(
Thank you for any help.

[jsulm]

@km2442 Did you execute qmake and a complete rebuild?

[km2442]

@jsulm Yes, I tried to clean my solution, qmake and build... But no effect :/

[ambershark]

@km2442 https://bugreports.qt.io/browse/QTBUG-56634

Looks like moc is failing to parse headers that have atlbase in them.

[km2442]

@ambershark Ok, So what should I do now? Download Qt 5.7, or wait for fix? I'm using atlbase library in some functions :/

[ambershark]

@km2442 In the past with bugs like that in Qt, I've just gone in and fixed it myself. It is probably pretty easy to fix.

Or you could wait for the Qt team to fix it.

Or you could downgrade to a Qt that doesn't have that issue.

Or you could not use atlbase in a header. Move it to your implementation file if possible and moc should be fine parsing the header. Or drop your reliance on atl completely.

[km2442]

@ambershark Thank you for advice. I had never edit Qt code, so I will downgrade and wait for update :)

[ambershark]

@km2442 said in Qt 5.8 can't compile, jom errors:

@ambershark Thank you for advice. I had never edit Qt code, so I will downgrade and wait for update :)

It's a little scary at first but it's usually very localized problems that you are trying to fix. I'm betting that fix would be a few lines of code/changes at most.

But downgrade is a good option too. :)

The bug is also already assigned to a developer so I'm betting it will be fixed on the next release. But since 5.8.0 just came out that could be a bit until 5.8.1.

[Pulller]

I meet the same issue today. So i download the older version of Qt.