Re: Getting Started -Makefile

[Esben Haabendal <eha@doredevelopment.dk>]

On Wed, 2007-11-21 at 19:57 +0200, Paul Sokolovsky wrote:
> Hello Esben,
> 
> Wednesday, November 21, 2007, 8:20:57 AM, you wrote:
> 
> []
> 
> >> 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.
> 
> > Something like that would be nice. When bitbake finds BBPATH unset, it
> > traverses from $PWD to / to find a .bbenv (or some other filename, but
> > local.conf is probably not a good one), which can setup BBPATH,
> > PYTHONPATH, OEDIR or whatever env virables is used in the
> > conf/local.conf file.
> 
>   LOL. So, editing .bashrc is hard, while creating and editing some
> obscure file is easy?

No, they are very much the same. And that is not the issue here.

The issue is as Rod also describes, the possibility to switch between
different OE build setups by switching directory. Further on, my
proposal would not dictate you to be in a specific directory, ie. the
build dir, to make bitbake behave as expected, but allow you to go to
any subdir of the build dir and have the same behavior as with the
current .bashrc or ". ./setup-env" approach.

> > To guard against bad bitbake versions (as BBPATH
> > is unset, bitbake can be expected to be picked up from a generic PATH)
> > it might be smart to introduce a variable in local.conf stating specific
> > or minimum version requirements for bitbake.
> 
>   ... Ah, and it comes at the expense yet?

Nothing is free. And I am certain that if it turns out the be a real
problem that people depend on different specific bitbake versions (I am
sorry, I don't know if this is a common situation today...), then we can
find a solution.

> > Would there by any problems in extending bitbake calling convention in
> > this way?
> 
>   Yes. Occam's blade. There's nothing to extend for. "man bash" will
> make everyone who does it an expert not only in bitbake, but in Unix
> way of doing stuff at all. After that, it will be much easier to
> decide if something worth fixing, if yes, then why, and finally, how.

I really fail to see your point here. Are you meaning to say that the
current solution with setting environment variables in .bashrc or
setup-env makes anybody a Unix expert?  I believe that all the other
skills require to work with OE is more demanding, so that this is not a
good reason for any kind of in-convenience.

Best regards,
Esben

-- 
Esben Haabendal
Embedded Software Consultant, Dore Development ApS
Phone: +45 5192 5393  Email: eha@doredevelopment.dk