> On 14 Mar 2015, at 11:42, Padam Jeet Singh <padam.si...@inventum.net> wrote: > > >> On 14-Mar-2015, at 5:05 pm, Paul Eggleton <paul.eggle...@linux.intel.com >> <mailto:paul.eggle...@linux.intel.com>> wrote: >> >> On Saturday 14 March 2015 12:51:31 Padam Jeet Singh wrote: >>> I am trying to build a custom layer on top of core-image-full-cmdline. >>> Basically I did this: >>> >>> 1. Created a new general layer using the yocto-layer command. This also >>> generated a simple hello world recipe. 2. Added that layer in the >>> conf/bblayers.conf BBLAYERS variable. >>> >>> Then I do a bitbake -v core-image-full-cmdline, and I don’t see >>> /usr/bin/helloworld in the final rootfs. >>> >>> Then I edit the conf/local.conf and add the following: >>> >>> IMAGE_INSTALL_append = " example” >>> >>> and then I can see the helloworld in the rootfs. >>> >>> Since I will be adding close to 50 recipes in this layer, isn’t there an >>> option where all recipes in that layer are included by default? Even if I >>> have to declare each recipe to be included, is there a place where I can >>> define those in my own layer configuration (layer.conf) rather than >>> local.conf? >> >> Firstly, I'd recommend you create your own custom image recipe(s) rather >> than >> adding packages via local.conf. > > This is exactly what I am trying to avoid - it’s unmaintainable.
Why do you think it is unmaintainable? Doesn't it just need to inherit core-image-fill-cmdline and add in the packages you need. > Secondly, the way to handle bringing in a >> large number of packages as a unit is to create a packagegroup recipe within >> your custom layer to pull in all the packages you want installed, and then >> you >> just need to add that packagegroup to your image. > > This sounds good. Would I be referring to this group via the > IMAGE_INSTALL_append = “ mygroup” ? > >> >> Cheers, >> Paul >> >> -- >> >> Paul Eggleton >> Intel Open Source Technology Centre > > Padam J. Singh | VP Engg. | Inventum Technologies Private Limited > www.inventum.net <http://www.inventum.net/> > +91.9810146640 > > Address: > C-70, Phase II Extension, > Noida 201305, UP, > India > > Tel : +91.120.4647000 > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. If > you have received this email in error please notify the system manager. This > message contains confidential information and is intended only for the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and delete > this e-mail from your system. If you are not the intended recipient you are > notified that disclosing, copying, distributing or taking any action in > reliance on the contents of this information is strictly prohibited. No > employee or agent is authorized to conclude any binding agreement on behalf > of [Inventum Technologies Private Limited] with another party by email > without express written confirmation by a whole-time Director of the Company > who has been authorized vide a valid board resolution to the effect. Our > company accepts no liability for the content of this email, or for the > consequences of any actions taken on the basis of the information provided, > unless that information is subsequently confirmed in writing. If you are not > the intended recipient you are notified that disclosing, copying, > distributing or taking any action in reliance on the contents of this > information is strictly prohibited. Any views or opinions presented in this > email are solely those of the author and do not necessarily represent those > of the company. Employees of [Inventum Technologies Private Limited] are > expressly required not to make defamatory statements and not to infringe or > authorize any infringement of copyright or any other legal right by email > communications. Any such communication is contrary to company policy and > outside the scope of the employment of the individual concerned. The company > will not accept any liability in respect of such communication, and the > employee responsible will be personally liable for any damages or other > liability arising. > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Chris Tapp opensou...@keylevel.com www.keylevel.com ---- You can tell you're getting older when your car insurance gets real cheap!
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
