Good news: Qt5.5 release notes indicate Qt3D is now (finally) included in the pre-built binaries, so it seems to be a legit component of Qt!
Bad news: It's been separated into a few submodules, so instead of just Qt3D there is now
- Qt3DCore
- Qt3DInput
- Qt3DRenderer
These two also start with Qt3D but I'm pretty sure Qt3DQuick was separate all along:
- Qt3DQuick
- Qt3DQuickRenderer
So this rather complicates the ability to build against Qt3D into three categories:
- Qt4
- Qt5 (up to 5.4)
- Qt5 (5.5+)
I've not actually found anything yet about this split (googling for Qt3DCore produces very few results), but assuming its the new structure going-forward, the question is whether to support all three of the above, or just the 'latest' state of Qt4 and Qt5.
Essentially, where we currently test for Qt4 vs Qt5 in snark's CMake, should I just switch the current Qt5 behaviour to be compatible with 5.5 only? or do we want to have 3 options (4, 5, 5.5+)?