From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [Bitbake-dev] A new bitbake extension: .bbappend files
Date: Tue, 3 Aug 2010 21:09:49 -0700 [thread overview]
Message-ID: <20100804040949.GA7085@gmail.com> (raw)
In-Reply-To: <1280842002.16235.83.camel@rex>
On (03/08/10 14:26), Richard Purdie wrote:
> On Fri, 2010-07-16 at 15:25 +0100, Richard Purdie wrote:
> > Whilst our layers mechanism, is great it does have a drawback which has
> > bugged me for a while. If you have a recipe like pointercal which has
> > machine specific information in it and you have your new machine code in
> > a layer, how do you add a pointercal file for your machine?
> >
> > Answer is you copy the whole pointercal recipe and files into your
> > layer, then add the single file for your machine. To me this is ugly,
> > ugly, ugly. We hate code duplication and as soon as you create two
> > copies of the same information, we've failed.
> >
> > So how could we do this better? Somehow we need to say that a given
> > directory X has some information which should be merged with the
> > original recipe. I've thought through several different ways of doing
> > this and the best solution I found was "bbappend".
> >
> > The idea is that if bitbake finds any X.bbappend files, when it loads
> > X.bb, it will also include these files after it parses the base .bb file
> > (but before finalise and the anonymous methods run). This means that
> > the .bbappend file can poke around and do whatever it might want to the
> > recipe to customise it.
> >
> > I went ahead and tried it out as its quite simple to code this in
> > bitbake. I liked the result enough I've already merged this into Poky:
> >
> > http://git.pokylinux.org/cgit.cgi/poky/commit/?id=63e6ba85677b8aa9f4cf9942a1fccbb8a8c72660
> >
> > I'm proposing to push it to bitbake master if there are no serious
> > objections.
>
> Whilst I think there were some initial concerns the consensus seemed to
> be that this was a good thing to have in bitbake, its something that has
> been on the feature wishlist since day one so I've merged the patch into
> bitbake master.
Now this fails.
$ bitbake -c clean -b virtual:native:/home/kraj/work/oe/openembedded/recipes/zlib/zlib_1.2.3.bb
Command execution failed: Traceback (most recent call last):
File "/home/kraj/work/oe/bitbake/lib/bb/command.py", line 88, in
runAsyncCommand
commandmethod(self.cmds_async, self, options)
File "/home/kraj/work/oe/bitbake/lib/bb/command.py", line 174, in
buildFile
command.cooker.buildFile(bfile, task)
File "/home/kraj/work/oe/bitbake/lib/bb/cooker.py", line 640, in
buildFile
the_data = self.bb_cache.loadDataFull(fn, self.get_file_appends(fn),
self.configuration.data)
File "/home/kraj/work/oe/bitbake/lib/bb/cooker.py", line 897, in
get_file_appends
if f in self.appendlist:
AttributeError: BBCooker instance has no attribute 'appendlist'
>
> Cheers,
>
> Richard
>
> _______________________________________________
> Bitbake-dev mailing list
> Bitbake-dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/bitbake-dev
next prev parent reply other threads:[~2010-08-04 4:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 14:25 A new bitbake extension: .bbappend files Richard Purdie
2010-07-16 14:35 ` George C. Huntington, III
2010-07-16 15:37 ` Carl Simonson
2010-07-16 15:46 ` [Bitbake-dev] " Michael Smith
2010-07-16 16:16 ` Chris Larson
2010-07-16 16:24 ` Richard Purdie
2010-07-16 16:53 ` Frans Meulenbroeks
2010-07-18 8:12 ` Esben Haabendal
2010-07-18 10:06 ` Detlef Vollmann
2010-07-18 15:13 ` Chris Larson
2010-07-18 16:01 ` Detlef Vollmann
2010-07-18 16:06 ` Chris Larson
2010-07-18 19:24 ` Detlef Vollmann
2010-07-18 20:25 ` Richard Purdie
2010-07-18 21:13 ` Detlef Vollmann
2010-07-19 8:31 ` Hauser, Wolfgang (external)
2010-07-18 19:47 ` Frans Meulenbroeks
2010-07-18 20:52 ` Chris Larson
2010-07-18 20:57 ` Frans Meulenbroeks
2010-07-19 0:02 ` Douglas Royds
2010-07-19 20:50 ` Tom Rini
2010-07-19 21:22 ` Chris Larson
2010-07-19 21:24 ` Chris Larson
2010-07-20 7:28 ` Frans Meulenbroeks
2010-07-20 14:06 ` Chris Larson
2010-07-20 15:19 ` Tom Rini
2010-07-20 15:50 ` Tom Rini
2010-07-20 15:52 ` Michael Smith
2010-07-20 16:06 ` Chris Larson
2010-07-20 16:29 ` Frans Meulenbroeks
2010-07-20 16:54 ` Chris Larson
2010-08-03 10:04 ` Frans Meulenbroeks
2010-08-03 12:53 ` Richard Purdie
2010-08-03 19:30 ` Khem Raj
2010-08-03 13:26 ` [Bitbake-dev] " Richard Purdie
2010-08-03 14:13 ` Chris Larson
2010-08-04 4:09 ` Khem Raj [this message]
2010-08-04 14:40 ` Richard Purdie
2010-08-04 19:00 ` Khem Raj
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=20100804040949.GA7085@gmail.com \
--to=raj.khem@gmail.com \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rpurdie@rpsys.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox