> -----Original Message----- > From: Carlos Enrique Pérez Sánchez <ceperez1...@gmail.com> > Sent: Friday, 26 April 2019 9:42 PM > To: Mitch Curtis <mitch.cur...@qt.io>; development@qt-project.org > Subject: Re: [Development] Qt Static Package > > > This sounds very similar to what I saw with linuxdeployqt a while back > Currently, I can link dynamically on Linux (using qmake to generate the > makefile) and make a standalone executable with linuxdeployqt and it works > well. I do have to add some dependencies manually like the svg module > (even if I add it to the .pro file) but after that it works well. > Regarding static builds, I have a few issues on Linux but none of them are > related directly to Qt. After install the corresponding -dev package the > related dependency issue is gone. However, it is hard to track all > dependencies and make another build every time something goes wrong > because I have a low-power device so the build process takes about 8 hours. > So, instead, I'm linking dynamically on Linux using linuxdeployqt. > > > I've sinced moved to Qbs, and for a while was building statically on Linux > and it solved all of the issues I had. Recently users started running into > issues > with missing ICU libs > I'm using qmake because there is not Qbs option in Qt 5.12 (at least on Linux, > opensource license). Also, I have zero experience with Qbs, but I will give > it a > try if you suggest so, but... > the command line options to pass to configure are exactly the same? > BTW: Can you post the command line you use to build Qt statically?
Here are my static configure args for Linux: -static -release -ltcg -opensource -confirm-license -nomake tests -nomake examples -silent _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development