Request: Qt3D in qt5-mac

[macports@…]

As I understand Qt3D is now effectively a proper module of Qt5, though not part of the default set if you download pre-built binaries from Qt (it is part of the default build if you build from git though).

Would it be possible to include Qt3D in qt5-mac, and/or add a variant to include this if there's any reason it's not appropriate for general use?

[mkae (Marko Käning)]

Cc Me!

[RJVB (René Bertin)]

Qt3D is not currently a component that is included in the tarball, so it would make more sense to provide it as a separate port for now and re-assess the situation if Qt 5.5 evolves to include it in the source tarball.

Qt5 is large enough as it is, and is meant to be built and shipped as separate components. I would be for keeping the main port comparable to the set included in Qt4 and Qt <= 5.3, but additional components that do not replace existing components should IMHO rather be provided as subports.

I'd invite you to create a port yourself (and submit it here), if you have experience building Qt3D and it doesn't require a lot of steps beyond the usual qmake && make combo (nor lots of dependencies not yet in MacPorts).

[macports@…]

actually the main reason I was hoping it could make its way into a port (either qt5-mac or a new separate port) is that I'm really struggling to build Qt5 with Qt3D from source, every release seems to have a slightly different build error for me

[RJVB (René Bertin)]

As reported in another ticket, I now provide a qt5-kde-devel port for Qt 5.5, which includes Qt3D (in the end it and qtcanvas weren't large enough to justify the hassle of creating more subports). I'm planning to sync qt5-kde to that version, and submit the result here.

I can imagine you're having issues: it took me about 3 days to upgrade my Qt5.4.2 port ...

[michaelld (Michael Dickens)]

Cc Me!

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

As of r142505, you can now install Qt3d as a submodule.
It is not part of qt5 Meta-port since it is still listed as "Technology Preview" at ​https://doc.qt.io/qt-5/qtmodules.html

[RJVB (René Bertin)]

Technology Preview or not, it's been considered mature enough to be built by default in Qt 5.5 ; providing it as a subport only serves to make the Qt5 Portfile more complex...

[macports@…]

if i'm not mistaken, Qt5 has been changed in macports to be entirely submodules (mimicking the structure of the Qt source itself), so Qt3D as a submodule seems to make sense given this new structure

(e.g. qt5-qtbase, qt5-qtdeclarative, qt5-qtmultimedia, etc)

[RJVB (René Bertin)]

Oh, indeed, that's just peachy, there's now a port:qt5 (and I'm actually even behind in version with my own ports). Indeed, in a set-up that reflects Qt's component structure it is perfectly logical to provide all components as subports. It even almost makes sense to have a subport for the sqlite plugin.

It's what I'm doing with my KF5 ports, but I intend to keep my own port:qt5-kde as it is in this aspect (= in line with qt4-mac). Breaking it up is too complex, with too little benefit for the perceived use which would lead to installing almost all subports anyway. At least both ports now install into libexec/qt5, which should make them binary compatible. Apparently I will have to add stub subports, though.