Hi, An important highlight below, regarding the use of toasterconf.json files.
Cheers, Alex On Fri, Jul 24, 2015 at 10:56 AM, Barros Pena, Belen < [email protected]> wrote: > > > On 24/07/2015 10:37, "[email protected] on behalf of > Haridasan, Sujith" <[email protected] on behalf of > [email protected]> wrote: > > >Hi All, > > > >Gentle ping . > > Hi Sujith: sorry for the delay in getting back to you. We don't deserve a > gentle ping: we need a hard poke! ;) > > Answer below. > > > >Any hint regarding my query? > > > > > >Thanks, > >Sujith H > > > >From: Haridasan, > > Sujith > >Sent: 23 July 2015 11:44 > >To: [email protected] > >Subject: Usage of already cloned layers in toaster > > > > > > > >Hi all, > > > >My query in yesterday¹s meeting was, let¹s say I have locally cloned > >layer for example: meta-qt5 and its dependencies like meta-ruby and > >meta-oe. > >Then would it be possible to use it with toaster (rather than toaster > >cloning layers by itself) ? > > You have 2 ways of doing this: > > 1. Use the import layer functionality. This is how: > > * In the project page, click the "import layer" link you will find below > the add layers text field. > * Provide the required information for meta-qt5, meta-ruby and meta-oe. > Note that: > > 1. Toaster will force you to rename the layers (for example to > meta-qt5-local or something like that) since Toaster requires layer names > to be unique. > 2. In the Git repository URL field, enter the full path to the local layer > you have cloned > 3. In the Revision field, enter the branch, tag or commit of the local > layers you want to use. You should also be able to set the revision to > HEAD here, and I believe that should use the tip of the current local > branch. Alex, please correct me if I am wrong > > If you import your own versions of meta-oe and meta-ruby before meta-qt5 > you can also set the layer dependencies for your meta-qt5-local to your > imported layers using the Layer dependencies at the bottom of the import > layer page. > > 2. The second way involves creating your own release by editing the > toasterconf.json file that you will find inside the meta-yocto layer, in > the /conf directory. In the releases section, create your own release, > following the format of the release called 'local', and setting the branch > and the default layers as you need them. Alex or Michael should be able to > give you more information on how to use this second option. > The important part here is to recognize that the toasterconf.json file is a *layer* configuration file, not a *toaster* configuration file. This means that if you have your own custom layer, you should create a toasterconf.json file for your layer, and import that into Toaster (using the *manage.py loadconf* command), rather than modifying other's layer configuration file. > > Let us know how you get on, and if you need anything else. > > Cheers > > Belén > > > >If so what would be the extra efforts that needs to be put. > >Let me know if more inputs are needed from me so that I can help team > >understand the requirement. > > > >Thanks, > >Sujith H > > > > -- > _______________________________________________ > toaster mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/toaster > -- Alex Damian Yocto Project SSG / OTC
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
