On Mon, Sep 22, 2014 at 8:02 AM, Ylinen, Mikko <[email protected]> wrote: > > > On Mon, Sep 22, 2014 at 5:48 PM, Dominig ar Foll <[email protected]> > wrote: >> >> 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. > > > This part is obvious. What's not is why the OBS config needs to > be "%define _with_qt5 0" even if the Qt libs are there. >
If the Qt libs are there, we should "%define _with_qt5 1" so that developers can use the AMB plugins that use Qt if they want (optional). If someone wants to build all tizen packages without Qt, they can "%define _with_qt5 0". By default it should be ON because developers want/need those optional packages and shouldn't have to rebuild AMB to get them. So I'm with Mikko on this one. --Kevron > -- Mikko > > > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
