What's the reason behind different config file in oe-layersetup

What's the reason behind different config file in oe-layersetup

[Ankur Tyagi]

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

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.

For a commercial product, which config should be used to create bsp, kernel
and rootfs

thanks
Ankur

[-- Attachment #2: Type: text/html, Size: 1402 bytes --]

Re: What's the reason behind different config file in oe-layersetup

[Denys Dmytriyenko]

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

Re: What's the reason behind different config file in oe-layersetup

[Ankur Tyagi]

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 3183 bytes --]

Re: What's the reason behind different config file in oe-layersetup

[Denys Dmytriyenko]

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
> >

Re: What's the reason behind different config file in oe-layersetup

[Ankur Tyagi]

[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]

Thanks for the help.


On Tue, Feb 2, 2016 at 11:22 AM, Denys Dmytriyenko <denys@ti.com> wrote:

> 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
> > >
>

[-- Attachment #2: Type: text/html, Size: 3603 bytes --]