[meta-freescale] [base][PATCH] setup-environment: Simplify use model for pre-existing build directory

[Otavio Salvador]

Hello Tudor,

On Wed, Nov 16, 2016 at 8:41 AM, Florea, Tudor
<tflorea at curtisswright.com> wrote:
> Poky already provide a versatile mechanism for setting up the build environment [1]:
> TEMPLATECONF=/path/to/my/conf .  [path_to]/oe-init-build-env [build_dir].
>
> Is it a particular reason to diverge from this?
>
> With this script I can no longer point to my template conf directory.
>
> The chances are that my machine, my distro name and my common target are all custom.
>
> I see that one think this script is doing is explicitly accepting the EULA (one time only).
> Most probably this is implicitly accepted as per the content of my/conf/local.conf.sample.  I assume I'm allowed to do this; is that true?
> For this purpose a separate script modifying the existing conf/local.conf is more simple and more intuitive.
> The same approach could be used for setting up the (SDK)MACHINE and DISTRO if those aren't already set on local.conf.sample
> The conf-notest.txt might issue the fact that above script(s) need to be run (once) to complete the environment setup.

The idea of our setup-environment script is to allow for easy use of
the FSL Community BSP. We are wide open to trim the script down, if it
keep supporting the current features and become more generic. Please
feel free to send any patches you have which help us to move on this
direction :-)

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750