We are actually using the commercial license. I downloaded the source package and am trying to build (and package) it internally so we can include it in various environments (docker images, say). I'm just following the official docs, and had no reason to not use the `qt-eveywhere-src` source package.
On Mon, Jan 9, 2023 at 3:00 PM Thiago Macieira <thiago.macie...@intel.com> wrote: > > On Monday, 9 January 2023 09:14:16 CST Stefan Seefeld wrote: > > lrelease error: cannot create > > '/home/user/srcdir/qt-build/build/qtbase/share/qt5/translations/qtwebsockets > > _en.qm': No such file or directory > > make[2]: *** > > [qttranslations/translations/CMakeFiles/updateqm-qtwebsockets_en.ts.dir/buil > > d.make:70: > > qttranslations/translations/CMakeFiles/updateqm-qtwebsockets_en.ts] Error 1 > > Please note our CI does not test the qt-everywhere tarball often. > > Prefer building each tarball individually instead. This also allows you to > build only those that you need and skip the modules you don't (e.g., > qtwebengine). > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest -- ...ich hab' noch einen Koffer in Berlin... _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
