From: Paul Sokolovsky <pmiscml@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Getting Started -Makefile
Date: Wed, 21 Nov 2007 04:24:05 +0200 [thread overview]
Message-ID: <617697824.20071121042405@gmail.com> (raw)
In-Reply-To: <4743201F.8000202@am.sony.com>
Hello Tim,
Tuesday, November 20, 2007, 7:57:51 PM, you 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?
This is attempt to put it backwards. It's not to allow bitbake
to be used outside of build directory, it's to allow *source* be
outside build directory. Real hardcore make users might have heard
about VPATH envvar and out-of-source building.
Why not default? Well, because what make builds is usually ones to
tens of megabytes, while bitbake builds tens to hundreds gigabytes.
Those who're brave to undertake such endeavour, are expected to get
some understanding of what they're going to be thru by learning and
doing some setup with their own hands. I'm sure that was original
motivation why bitbake and OE was setup that way. Of course, that was
quite some time ago, when disks were much smaller. Let's see if this
will change now.
> -- Tim
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-11-21 4:11 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 12:08 Getting Started -Makefile David Farning
2007-11-19 14:33 ` Koen Kooi
2007-11-19 23:51 ` Rod Whitby
2007-11-20 9:12 ` pHilipp Zabel
2007-11-20 17:57 ` Tim Bird
2007-11-20 20:00 ` Cliff Brake
2007-11-20 20:38 ` Philip Balister
2007-11-20 23:25 ` Florian Boor
2007-11-21 2:24 ` Paul Sokolovsky
2007-11-21 3:38 ` Rod Whitby
2007-11-21 2:24 ` Paul Sokolovsky [this message]
2007-11-21 5:44 ` Rod Whitby
2007-11-21 17:45 ` Paul Sokolovsky
2007-11-22 1:35 ` Michael 'Mickey' Lauer
2007-11-22 4:20 ` Lorn Potter
2007-11-22 8:14 ` Esben Haabendal
2007-11-23 1:05 ` Lorn Potter
2007-11-21 17:58 ` Tim Bird
2007-11-21 18:29 ` Paul Sokolovsky
2007-11-21 23:17 ` Rod Whitby
2007-11-22 0:44 ` Tim Bird
2007-11-22 20:29 ` Paul Sokolovsky
2007-11-21 19:32 ` Philip Balister
2007-11-21 19:32 ` Philip Balister
2007-11-20 21:16 ` Rod Whitby
2007-11-21 6:20 ` Esben Haabendal
2007-11-21 17:57 ` Paul Sokolovsky
2007-11-21 23:04 ` Rod Whitby
2007-11-22 8:40 ` Esben Haabendal
2007-11-20 9:39 ` Richard Purdie
2007-11-20 11:06 ` Rod Whitby
2007-11-20 12:30 ` Koen Kooi
2007-11-20 21:20 ` Rod Whitby
2007-11-20 9:58 ` Koen Kooi
2007-11-20 11:11 ` Rod Whitby
2007-11-20 12:27 ` Koen Kooi
2007-11-20 21:19 ` Rod Whitby
2007-11-20 14:39 ` Paul Sokolovsky
2007-11-20 23:20 ` Florian Boor
2007-11-20 11:44 ` Rod Whitby
2007-11-20 13:10 ` Koen Kooi
2007-11-20 21:11 ` Rod Whitby
2007-11-20 23:06 ` Lorn Potter
2007-11-19 14:41 ` Holger Freyther
2007-11-19 18:32 ` Tobias Pflug
2007-11-19 21:08 ` Lorn Potter
2007-11-20 9:33 ` Richard Purdie
2007-11-20 10:46 ` Marcin Juszkiewicz
2007-11-20 15:32 ` Mike (mwester)
2007-11-20 17:04 ` Marcin Juszkiewicz
2007-11-20 17:29 ` Holger Freyther
2007-11-20 17:29 ` Koen Kooi
2007-11-20 23:12 ` Lorn Potter
2007-11-22 1:32 ` Michael 'Mickey' Lauer
2007-11-22 1:28 ` The truth about OE team being afraid of 'make' (was: Getting Started -Makefile) Michael 'Mickey' Lauer
2007-11-22 3:15 ` Chris Larson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=617697824.20071121042405@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tim.bird@am.sony.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.