[oe] Getting Started -Makefile

[Rod Whitby]

pHilipp Zabel wrote:
> So why not provide a simple shell wrapper instead of setup-env and the
> Makefile's build-package-% part? That way, at least people would learn
> the correct bitbake syntax from the beginning.
> 
> $ cat ~/bin/bitbake
> #!/bin/sh
> export OEDIR=${OEDIR:-$PWD}
> export BBPATH=${BBPATH:-$OEDIR/build:$OEDIR/openembedded}
> /usr/local/bin/bitbake $*
>
>> If we can fix the underlying problem (needing to type more than one
>> command to build an image with bitbake), then I will fully support a
>> move to get rid of all bitbake wrappers from all the Makefiles that I
>> manage.
> 
> The question is how to fix this problem correctly.
> One possibility would be that bitbake, if BBPATH is unset, issues a
> warning and scans the file system (starting from the $PWD) for a
> certain file (local.conf) in which BBPATH would be specified.

Finally, someone who wants to help solve the problem, rather than just
dump on other development practices.  Thank you Philipp.

I personally feel that there should be a standard directory structure
mandated by OE (instead of just leaving it up to each developer to
choose how they want to set up OE this week), so that default behaviour
like the above can be added, and so that new users can be assisted
without needing to guess at what their directory structure and default
values are.

Part of the rationale for the Makefile setup is that you then have a
large group of developers who are all doing things *exactly* the same
way, with the same directory structure and same default contents of
configuration files.  That is a powerful way to assist new users and
make sure that problems in the build setup are found quickly, and that
solutions to those problems can be distributed just as quickly.

-- Rod