|
override SITEINFO_BITS?
Hi, First time building Yocto (but have been using OE) on an openSUSE 11.4 64-bit host: $ bitbake core-image-minimal One of the first steps is to build pseudo-native. As it turns out I have the glibc-
Hi, First time building Yocto (but have been using OE) on an openSUSE 11.4 64-bit host: $ bitbake core-image-minimal One of the first steps is to build pseudo-native. As it turns out I have the glibc-
|
By
Trevor Woerner
· #3655
·
|
|
override SITEINFO_BITS?
Ah, thanks. That's what I needed.
Ah, thanks. That's what I needed.
|
By
Trevor Woerner
· #3657
·
|
|
Variable locality too restricted.
<richard.purdie@...> wrote: Would it be possible to have both kernels built and installed to the image with the PREFERRED_PROVIDER selecting the default kernel to boot (i.e. grub/lilo/
<richard.purdie@...> wrote: Would it be possible to have both kernels built and installed to the image with the PREFERRED_PROVIDER selecting the default kernel to boot (i.e. grub/lilo/
|
By
Trevor Woerner
· #3759
·
|
|
Variable locality too restricted.
<richard.purdie@...> wrote: Isn't this the default behaviour (i.e. sstate checksums enabled on the stamp files)?
<richard.purdie@...> wrote: Isn't this the default behaviour (i.e. sstate checksums enabled on the stamp files)?
|
By
Trevor Woerner
· #3771
·
|
|
[PATCH 1/2] Fix Makefiles
Agree. Additionally, "make distcheck" will generally fail if there is no DESTDIR.
Agree. Additionally, "make distcheck" will generally fail if there is no DESTDIR.
|
By
Trevor Woerner
· #4087
·
|
|
Hob workflow
Hi everyone, I've been using Hob lately and I'm completely blown away by how useful it is! Kudos to everyone: from those insisting there exist such a tool to those working on it :-) While using it, ho
Hi everyone, I've been using Hob lately and I'm completely blown away by how useful it is! Kudos to everyone: from those insisting there exist such a tool to those working on it :-) While using it, ho
|
By
Trevor Woerner
· #8512
·
|
|
Questions about 'bitbake core-image-minimal'
The job of automake/automake is just to create the Makefiles which the "make" utility can use to compile software; this is but one small component in the overall task of cross-compiling software for a
The job of automake/automake is just to create the Makefiles which the "make" utility can use to compile software; this is but one small component in the overall task of cross-compiling software for a
|
By
Trevor Woerner
· #8573
·
|
|
Hob workflow
Hi Jessica, Thanks so much for considering my feedback :-) I do tend to be "wordy", don't I? :-) No, I think you've captured everything quite succinctly. Expanding on point 1 a little bit: Due to the
Hi Jessica, Thanks so much for considering my feedback :-) I do tend to be "wordy", don't I? :-) No, I think you've captured everything quite succinctly. Expanding on point 1 a little bit: Due to the
|
By
Trevor Woerner
· #8617
·
|
|
Hob workflow
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2934 https://bugzilla.yoctoproject.org/show_bug.cgi?id=2935
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2934 https://bugzilla.yoctoproject.org/show_bug.cgi?id=2935
|
By
Trevor Woerner
· #8621
·
|
|
layer.conf: "packages" directory
Hi, In the Yocto Project Development Manual, section 4.1.2 "Creating Your Own Layer" it shows an example layer.conf file. In this example, right before adding the recipes to BBFILES, appears the comme
Hi, In the Yocto Project Development Manual, section 4.1.2 "Creating Your Own Layer" it shows an example layer.conf file. In this example, right before adding the recipes to BBFILES, appears the comme
|
By
Trevor Woerner
· #8636
·
|
|
[PATCH poky] layer.conf: clarify comments
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- document
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- document
|
By
Trevor Woerner
· #8669
·
|
|
[PATCH poky-extras] layer.conf: clarify comments
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- meta-ker
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- meta-ker
|
By
Trevor Woerner
· #8670
·
|
|
[PATCH meta-intel] layer.conf: clarify comments
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- conf/lay
From: Trevor Woerner <twoerner@...> The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@...> --- conf/lay
|
By
Trevor Woerner
· #8671
·
|
|
[PATCH poky-extras] layer.conf: clarify comments
Hi Bruce, <bruce.ashfield@...> wrote: Awesome, thanks. Any word on whether the other two can be applied as well? The one for meta-intel and the one for the poky base? Best regards, Trevor
Hi Bruce, <bruce.ashfield@...> wrote: Awesome, thanks. Any word on whether the other two can be applied as well? The one for meta-intel and the one for the poky base? Best regards, Trevor
|
By
Trevor Woerner
· #8680
·
|
|
knotty2
Wow! The new cmdline interface (which I assume is knotty2?) is _really_ impressive!
Wow! The new cmdline interface (which I assume is knotty2?) is _really_ impressive!
|
By
Trevor Woerner
· #8755
·
|
|
of recipes and packages
Okay, if the confusion over "yocto" versus "yocto project" versus "poky" and trying to decide whether poky or yocto is a distribution or a build system or sometimes both or neither of either wasn't ba
Okay, if the confusion over "yocto" versus "yocto project" versus "poky" and trying to decide whether poky or yocto is a distribution or a build system or sometimes both or neither of either wasn't ba
|
By
Trevor Woerner
· #8859
·
|
|
of recipes and packages
Hi Jeff, Thanks for your tasty metaphors! But your wording would seem to imply _a_ recipe builds _a_ package. But a recipe doesn't build a package, a recipe potentially builds lots of packages. For ex
Hi Jeff, Thanks for your tasty metaphors! But your wording would seem to imply _a_ recipe builds _a_ package. But a recipe doesn't build a package, a recipe potentially builds lots of packages. For ex
|
By
Trevor Woerner
· #8866
·
|
|
of recipes and packages
Do the OE people accept this wording too, or is this a yocto-project-only thing? In other words, should a potential patch be sent to OE or here?
Do the OE people accept this wording too, or is this a yocto-project-only thing? In other words, should a potential patch be sent to OE or here?
|
By
Trevor Woerner
· #8869
·
|
|
microcontroller central article
A short blog entry about the Yocto Project was just posted on the "microcontroller central" website: http://www.microcontrollercentral.com/author.asp?section_id=1741&doc_id=249581
A short blog entry about the Yocto Project was just posted on the "microcontroller central" website: http://www.microcontrollercentral.com/author.asp?section_id=1741&doc_id=249581
|
By
Trevor Woerner
· #8890
·
|
|
of recipes and packages
<paul.eggleton@...> wrote: So should I send in a patch against the Yocto Project's poky/bitbake/bin/bitbake or try to have it accepted upstream?
<paul.eggleton@...> wrote: So should I send in a patch against the Yocto Project's poky/bitbake/bin/bitbake or try to have it accepted upstream?
|
By
Trevor Woerner
· #8915
·
|