On Thu, Oct 23, 2014 at 6:31 AM, Damian Hobson-Garcia <[email protected]> wrote:
> Hi Mikko, > On 2014-10-21 2:24 PM, Ylinen, Mikko wrote: > > On Mon, Oct 20, 2014 at 11:34 AM, Damian Hobson-Garcia < > [email protected]> > >>> The .spec file could also have multiple defconfigs for arm and then > each > >>> profile > >>> can select the default one using a bcond option. > >> Does selecting one image using bcond require multiple targets? > >> > >> > > Yes > > Just to clarify, having multiple targets (board.confs) implies multiple > repos, correct? That would seem to impact the scalability. Instead of > multiple targets, is it possible to have multiple packages, one for each > kernel variant, and have them all sit in the same repo, with the ks file > doing the selection? > It'd be easy if we had multiple Git trees too. Trying to do the same from a single Git tree adds more complexity. Build variables are 'profile' and 'arch' but they are fixed for one target. I don't think rpmbuild easily supports building the same binary name with different options (defconfigs). Or at least the .spec scripting would become very complex. -- Mikko
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
