30.01.2017, 20:58, "mark diener" <rpzrpz...@gmail.com>:
> Kai:
>
> Thank you for the response.
>
> As a QT customer, I would hope that communications from Qt Staff would
> yield something that I can USE.
>
> Your response suggested that dependency build failures are an uncommon
> occurrence. ("there might still be feature permutations that lead to
> compilation errors")
>
> I can assure you that 100% of my attempts to reduce the binary size of
> Qt 5.8 have ended in failure.
>
> Don't believe me? Try this test config line:I think macOS is not the best platform to play with shrinking, try Linux instead. > > /macdev/qt580/5.8/Src/configure -prefix /macdev/qt580/5.8/osxstat \ > -verbose \ > -opensource \ > -release \ > -strip \ > -c++std c++11 \ > -confirm-license \ > -reduce-exports \ > -nomake tests \ > -nomake examples \ > -qt-libjpeg \ > -qt-libpng \ > -opengl desktop \ > -no-widgets > > Results in build failure: > > 10.11.sdk/System/Library/Frameworks/AGL.framework/Headers > -I/macdev/qt580/5.8/Src/qtbase/mkspecs/macx-clang > -F/macdev/qt580/5.8/build-osx/qtbase/lib -o .obj/qmacfunctions_mac.o > /macdev/qt580/5.8/Src/qtmacextras/src/macextras/qmacfunctions_mac.mm > In file included from > /macdev/qt580/5.8/Src/qtmacextras/src/macextras/qmacfunctions_mac.mm:50: > In file included from /macdev/qt580/5.8/Src/qtbase/include/QtWidgets/QMenu:1: > In file included from > /macdev/qt580/5.8/Src/qtbase/include/QtWidgets/qmenu.h:1: > In file included from > /macdev/qt580/5.8/Src/qtbase/include/QtWidgets/../../src/widgets/widgets/qmenu.h:43: > In file included from > /macdev/qt580/5.8/Src/qtbase/include/QtWidgets/qtwidgetsglobal.h:1: > /macdev/qt580/5.8/Src/qtbase/include/QtWidgets/../../src/widgets/kernel/qtwidgetsglobal.h:44:10: > fatal error: 'QtWidgets/qtwidgets-config.h' file not > found > #include <QtWidgets/qtwidgets-config.h> > ^ > 1 error generated. > make[3]: *** [.obj/qmacfunctions_mac.o] Error 1 > make[2]: *** [sub-macextras-install_subtargets] Error 2 > make[1]: *** [sub-src-install_subtargets] Error 2 > make: *** [module-qtmacextras-install_subtargets] Error 2 > Start:Mon Jan 30 11:40:59 CST 2017 End:Mon Jan 30 11:52:37 CST 2017 > mds-Mac-mini:builds md$ > > So how do I get rid of widgets, since I am only using Qt Quick QML? > > Maybe Qt can provide configuration command line examples of reduced > size builds that actually WORK. > > Thanks > > md > > On Mon, Jan 30, 2017 at 9:12 AM, Kai, Koehne <kai.koe...@qt.io> wrote: >>> -----Original Message----- >>> From: mark diener [mailto:rpzrpz...@gmail.com] >>> Sent: Monday, January 30, 2017 3:05 PM >>> To: Tor Arne, Vestbø <tor.arne.ves...@qt.io> >>> Cc: Kai, Koehne <kai.koe...@qt.io>; interest@qt-project.org; Jake, >>> Petroules <jake.petrou...@qt.io> >>> Subject: Re: Qt Lite 5.8 >>> >>> Ok, >>> >>> Maybe someone at Qt could direct us to the Qt Lite documention? >> >> Qt Lite isn't a product, but an initiative (see also the original >> announcement at >> http://blog.qt.io/blog/2016/08/18/introducing-the-qt-lite-project-qt-for-any-platform-any-thing-any-size/ >> ). As such there's no 'Qt Lite documentation'. >> >> Anyhow, the part of Qt Lite that you might refer to is the rework of the Qt >> configuration system. Qt always had configure arguments for some features, >> but they were hard-coded in the configure script, and mostly limited to the >> libraries in qtbase. There was also a feature system based on a >> qfeatures.txt file, which however was not getting much attention and >> deteriorated over time. >> >> We now have a modular system where every Qt module can declare its options >> and features (including dependencies) in a declarative 'configure.json' >> file. These features can then be switched on and off from the top-level >> configure call. A lot of the Qt modules already make use of this to allow >> developers to enable or disable features that weren't exposed before. >> >> There's also a graphical tool that shows the features (currently only for >> Qt for Device creation): >> http://doc.qt.io/QtForDeviceCreation/qt-configuration-tool.html . You can >> also look up features through the configure.json files in the sources. >> >>> Or any information about it so that your customers can be successful. >>> >>> Right now, there is only dependency build failure hell. >> >> The new system doesn't guarantee that feature dependencies are always >> correctly represented, and there might still be feature permutations that >> lead to compilation errors. But the new setup should help us maintaining and >> fixing the dependencies much more easily, as well as adding new ones. >> >> Regards >> >> Kai > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest -- Regards, Konstantin _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
