https://github.com/pturley0/bitbake-hello-world
On Oct 9, 2012, at 5:56 PM, McClintock Matthew-B29882
wrote:
> On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
> wrote:
>> Success. The file tree depicted at the bottom of this mail is nearly the
>> smallest, valid BitBake project that prints "Hel
It helps a lot if you run it from the build dir. :-%
build% ../../bitbake/bin/bitbake a
Parsing recipes: 100%
|#|
Time: 00:00:00
Parsing of 1 .bb files complete (0 cached, 1 parsed). 1 targets, 0
skipped, 0 masked, 0 e
Again, thanks *so* much for putting this together. I tried to do this
once before and didn't have the tenacity to stick with it--it is a
surprisingly daunting task. Having a smallest-possible example will, I
think, be really helpful to developers who want to learn how to debug
bitbake and contribut
That's a perfectly reasonable suggestion, and a good excuse for me to open a
github account and learn how to use it :)
On Oct 9, 2012, at 5:56 PM, McClintock Matthew-B29882
wrote:
> On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
> wrote:
>> Success. The file tree depicted at the bottom of thi
On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
wrote:
> Success. The file tree depicted at the bottom of this mail is nearly the
> smallest, valid BitBake project that prints "Hello, World!" Here's the
> output:
Perhaps you could push this to github somewhere as an example?
-M
>
>
> $ ../Bi
Success. The file tree depicted at the bottom of this mail is nearly the
smallest, valid BitBake project that prints "Hello, World!" Here's the output:
$ ../BitBake/bin/bitbake a
Parsing recipes: 100%
|#| Time: 00:00:00
Pa
The T variable points to a directory were Bitbake places temporary files
when building a particular package. It is typically set to
T = ${WORKDIR}/temp
WORKDIR is the directory into which Bitbake unpacks and builds a package.
The default bitbake.conf file sets this variable.
T is not to be confu
I am continuing my work on creating a "Hello, World!" BitBake project. Because
of the excellent help I got before, things have gone reasonably well, but I'm
again running into something I don't know how to fix.
As before, the entire contents of my very small project appear at the end of
this me
>> Tasks must be Python functions.
>>
>>
> No, they can be shell functions too.
Probably worth adding that if you are doing an _append() on a task
function, you have to match the original function type. E.g., if you
want to append a shell snippet to a python task function, you need to do
On Thu, 2012-10-04 at 20:00 -0700, Rudolf Streif wrote:
> Disclaimer: I am no Bitbake expert. I just put this together by
> rummaging through the Bitbake code for a couple of minutes. I am
> reasonably confident that what I am saying below is rather accurate
> but the Bitbake experts know better.
>
> And one final question: Have I been putting this on the wrong mailing
list?
Possibly, kind of, but you would not have gotten my response because I do
not follow to bitbake-devel :)
:rjs
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yocto
> And one final question: Have I been putting this on the wrong mailing
list?
Kind of, but you would not have gotten my response because I do not
subscribe to bitbake-devel :)
:rjs
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject
Disclaimer: I am no Bitbake expert. I just put this together by rummaging
through the Bitbake code for a couple of minutes. I am reasonably confident
that what I am saying below is rather accurate but the Bitbake experts know
better.
Indeed it is. One of my first tasks will be to *remove* as muc
And one final question: Have I been putting this on the wrong mailing list?
I just discovered the mailing lists at OpenEmbedded, specifically:
bitbake-de...@lists.openembedded.org
Apologies if I've been bothering the wrong people.
On Oct 4, 2012, at 7:47 PM, Patrick Turley
wrote:
> *Very
*Very* helpful stuff.
I have re-created the tree you described, and everything seems to work. In
particular, bitbake-layers seems happy. I tried executing it against BitBake
1.12.0 and it succeeded. FYI, it failed against the current BitBake master,
which is 1.16.0.
I have some additional que
Thanks, this is great! I was looking for something exactly like this.
I'm going to have a play wit it right now. If you (or anyone) can think
of any ways this example doesn't adhere to current bitbake best
practices (other than not inheriting from OECore's more full-featured
base classes), please
[Warning: lengthy post, and probably boring to most.]
My Bitbake "Hello World" is a little more than a basic "Hello World". It's
idea is to incorporate a layer and use a structure similar to what OE and
Yocto are using. You can do it simpler if you want to. I did this a while
ago with Bitbake 1.12
That is excellent news. I very much look forward to seeing that.
On Oct 3, 2012, at 6:03 PM, Rudolf Streif
mailto:rudolf.str...@linux.com>>
wrote:
Hi Patrick,
I think I understand what you are looking for. I created this Bitbake Hello
World for a training class. It just uses 'raw' Bitbake an
Hi Patrick,
I think I understand what you are looking for. I created this Bitbake Hello
World for a training class. It just uses 'raw' Bitbake and a very basic
recipe to build the Nano editor (including download from the project site).
You need to have a couple of things in place to make this wor
In my previous message, some of the indentation in the representation of
my file tree was wrong (because we're using Outlook, which destroy all
indentation when you paste it into an e-mail message). The errors are
small, but I want to avoid annoying anyone who might think I don't even
have the file
I'll start with my question (so you can decide whether you care to read
the rest):
What is the BitBake equivalent of "Hello, World!?"
Specifically, what is the minimum project structure that
correctly describes a single layer and a single recipe?
---
21 matches
Mail list logo
