All of lore.kernel.org
 help / color / mirror / Atom feed
From: skorpyon1992 <skorpyon1992@yahoo.com>
To: yocto@yoctoproject.org
Subject: TEMPLATECONF for multiple devices
Date: Fri, 23 Sep 2016 14:46:39 +0300	[thread overview]
Message-ID: <57E5161F.80500@yahoo.com> (raw)

      Hello everyone,

      I started to build linux distributions for different devices and I 
would like to write some scripts that automatically clones git 
repositories  (poky, necessary layers, etc) and build the final image 
for the desired device. The configuration templates (provided from my 
custom layer) are the same for all devices except the MACHINE variable.
  Until now, for testing, I have manually set the TEMPLATECONF path 
(export TEMPLATECONF= path-to-my-layer/meta-mylayer/conf source 
poky/oe-init-build-env build-mydevice) and modified the local.conf with 
the correspondant  MACHINE name before creating any image.

   What would it be the best practice to minimize the configuration 
part? Use the same template configurations and modify the variables (in 
this case the MACHINE variable) after? Or have separate template 
configurations for each device inside my layer?

     Thanks in advance!


                 reply	other threads:[~2016-09-23 11:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57E5161F.80500@yahoo.com \
    --to=skorpyon1992@yahoo.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.