Re: Getting Started -Makefile

[Philip Balister <philip@balister.org>]

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

Make reads it's behavior from a Makefile.

Bitbake contains specific behaviors and reads some configuration from disk.

I don't think they are very similar. I kind of like not caring where I 
run bitbake from and being able to switch build trees by changing the 
environment.

Although I do see some merits to Tim's question, especially if it solves 
real-world problems.  (I mean really solve, not just mask)

Philip

Tim Bird wrote:
> pHilipp Zabel wrote:
>> $ cat ~/bin/bitbake
>> #!/bin/sh
>> export OEDIR=${OEDIR:-$PWD}
>> export BBPATH=${BBPATH:-$OEDIR/build:$OEDIR/openembedded}
>> /usr/local/bin/bitbake $*
> 
> This is nice.  Can someone tell me why this isn't
> the default behavior of bitbake now?  (I'm honestly
> not trolling :-)   There must be some good reason
> to allow bitbake to be used outside of a build
> directory.  Make (which bitbake resembles
> in some aspects), is sensitive to it's starting
> directory.  Why not bitbake?
>  -- Tim
> 
> =============================
> Tim Bird
> Architecture Group Chair, CE Linux Forum
> Senior Staff Engineer, Sony Corporation of America
> =============================
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]