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

[Denys Dmytriyenko <denys@ti.com>]

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