From: Denys Dmytriyenko <denys@ti.com>
To: Ankur Tyagi <ankur.tyagi85@gmail.com>
Cc: meta-arago@arago-project.org
Subject: Re: What's the reason behind different config file in oe-layersetup
Date: Mon, 1 Feb 2016 17:22:42 -0500 [thread overview]
Message-ID: <20160201222242.GW11314@edge> (raw)
In-Reply-To: <CADySD0GthGnaKrt+R=4azdPffVYWWz33hehvQP2gKjzZuUpDEg@mail.gmail.com>
I would recommend starting from arago-fido-config.txt and pin down all layers
later, once your own development stabilizes and you are ready to make your
release. You can also start with one of the latest coresdk or processor-sdk
configs as well, but you maybe missing some of the important bugfixes from
different layers that could be made during your development cycle...
--
Denys
On Tue, Feb 02, 2016 at 11:16:26AM +1300, Ankur Tyagi wrote:
> Thanks for explaining it.
>
> I am using am335x-evm as reference platform, so as per the link, I should
> be using amsdk-08.00.00.00-config.txt but it is based on daisy branch.
> Whereas processor-sdk-02.00.01.07-config.txt looks updated one.
>
> So is it ok to refer to processor-sdk to create my own ?
>
> thanks
>
>
> On Tue, Feb 2, 2016 at 10:58 AM, Denys Dmytriyenko <denys@ti.com> wrote:
>
> > On Tue, Feb 02, 2016 at 10:45:43AM +1300, Ankur Tyagi wrote:
> > > Hi,
> > >
> > > oe-layersetup has different set of configs. I couldn't find any
> > > documentation explaining "when to use which config".
> > >
> > > Can someone help me understand the rationale behind these configs ? They
> > > all refer to different commits of same repo, so I am sure there must a
> > > reason behind it.
> >
> > http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment
> >
> > Available Layer Configurations section explains what those configs are.
> >
> > To summarize - config files in the main configs/ directory are all
> > "rolling",
> > i.e. they pull latest from corresponding branches of all the layers. Useful
> > for development. On the other hand, configs in coresdk, amsdk, glsdk, mcsdk
> > and processor-sdk directories are the release configs, i.e. they pin down
> > all
> > the layers to a specific commit ID at the time of release. That way a given
> > release can be reproduced later on. And those SDK names are just product
> > names
> > to support corresponding TI embedded processor platforms.
> >
> >
> > > For a commercial product, which config should be used to create bsp,
> > kernel
> > > and rootfs
> >
> > For your own commercial product, you should create your own config, using
> > one
> > of the existing ones as an example.
> >
> > --
> > Denys
> >
next prev parent reply other threads:[~2016-02-01 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 21:45 What's the reason behind different config file in oe-layersetup Ankur Tyagi
2016-02-01 21:58 ` Denys Dmytriyenko
2016-02-01 22:16 ` Ankur Tyagi
2016-02-01 22:22 ` Denys Dmytriyenko [this message]
2016-02-01 22:25 ` Ankur Tyagi
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=20160201222242.GW11314@edge \
--to=denys@ti.com \
--cc=ankur.tyagi85@gmail.com \
--cc=meta-arago@arago-project.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.