Thiago, the problem is not to disable qt in the tizen.org but to allow the system to be consistent when a platform developer creates its own platform and rebuild his own Tizen without requiring qt
With the current model anyone needs to rebuild qt even if not used. In particular in the Tizen-Meta when building with Yocto, it adds a serious extra time for building even if not used. Ronan's proposition is simply to allow by a configuration to request not to build qt if not required. It will have no effect on the the tizen.org build or images, but will allow to seriously optimise the build time when a local build of Tizen is required and qt not desired (in particular when using Yocto). Regards Dominig Le 22/09/2014 16:36, Thiago Macieira a écrit : > On Monday 22 September 2014 15:04:36 Ylinen, Mikko wrote: >> Thus, as long as QT libs are in the repo, AMB can enable it's Qt based >> plugins too. > The build should always enable the Qt libs and the AMB plugins using Qt. The > plugins should be packaged in a separate .rpm from the rest of AMB plugins. > > If some IVI customer does not want Qt installed, they won't install neither > Qt > nor the plugins. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
