> I have difficulties to follow here. Could you expand?
Sorry for this. After seeing your mail I remembered that I disabled the Qbs
plugin about two years ago. My mistake. I re-enable it and it now appears
as another Build System option in the New Project Wizard. Thanks.
El vie., 26 abr. 2019 a
On Fri, Apr 26, 2019 at 03:42:17PM -0400, Carlos Enrique Pérez Sánchez wrote:
> I'm using qmake because there is not Qbs option in Qt 5.12 (at least on
> Linux, opensource license).
I have difficulties to follow here. Could you expand?
I.e. why is QBS not an option, how is that related to a spec
> We’re successfully building Qt Quick Controls 2 statically for the
WebAssembly target, so it should be possible.
Agree. I know some applications that use static builds of QQC2. By the way,
what platform are you using
> I don’t think we’re doing anything special. The test cases include the
“gal
> Note that CMake is notoriously bad when you want to build static
applications. It always prefers shared libraries when searching for
dependencies if they are present in the system.
I strongly agree. That's why I'm back to qmake. I hope that the people of
Qt Company add support for static builds
26.04.2019, 22:47, "Carlos Enrique Pérez Sánchez" :
>> 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
> 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 i