Hi,
I've a question regarding the BBLAYERS variable.
Is it possible to set some kind of a SRCREV (= git tag/branch/commit-id) for a
path listed in BBLAYERS?
I came to this question because I've two different branches in my meta layer:
one for development and one for 'stable' releases.
Therefore
Hi Richard,
On Monday 03 February 2014 12:17:04 Richard Leitner - SKIDATA wrote:
I've a question regarding the BBLAYERS variable.
Is it possible to set some kind of a SRCREV (= git tag/branch/commit-id)
for a path listed in BBLAYERS?
I came to this question because I've two different
Hi Paul,
thanks for your quick answer!
I'll work with separate checkouts for now...
But now I've got another question:
Is there any possibility to submit something like a feature request for this?
And is there a (realistic) chance that this feature gets implemented?
If so, where should this
Hi,
Hi Paul,
thanks for your quick answer!
I'll work with separate checkouts for now...
But now I've got another question:
Is there any possibility to submit something like a feature request for this?
And is there a (realistic) chance that this feature gets implemented?
If so, where
On 02/03/14 10:20, Christian Ege wrote:
But now I've got another question:
Is there any possibility to submit something like a feature request for this?
And is there a (realistic) chance that this feature gets implemented?
If so, where should this request go? To the bitbake-devel list?
I am
Hello,
I am adding OE-Core and Yocto mailing list as destination as this has
fixes for both.
While setting a build system, in a very clean host installation I
found some issues which were fixed in master and ought to be
backported to Dora:
meta-yocto:
- 1893d1576c1e7acc9881b3392a838c575019f18d
arm1176jzfshf uses -mtune=hard.
Add -mfpu=vfp if vfp is included in TUNE_FEATURES
---
conf/machine/include/tune-arm1176jzf-s.inc |7 +++
1 file changed, 7 insertions(+)
diff --git a/conf/machine/include/tune-arm1176jzf-s.inc
b/conf/machine/include/tune-arm1176jzf-s.inc
index
Hi,
I am building an image for an embedded system using the chiefriver and
kernel 3.12.9. I am using Ubuntu as our base system.
The image builds and boots fine which is great but we have some binaries
built on Ubuntu which must run on the Yocto image. When we copy these
across and try and run
On 3 February 2014 05:13, Padam J. Singh m...@padamj.com wrote:
What could be the possible reasons for a recipe to get packaged correctly in
an
RPM, shows as being installed in the final image generation, yet none of the
files actually
show up in the rootfs?
That's a very good question,
On Mon, Feb 3, 2014 at 4:28 PM, Christian Ege k423...@gmail.com wrote:
Hi,
Hi,
I am building an image for an embedded system using the chiefriver and
kernel 3.12.9. I am using Ubuntu as our base system.
The image builds and boots fine which is great but we have some binaries
built on
On 2014-02-03 09:59, David Welch wrote:
On Mon, Feb 3, 2014 at 4:28 PM, Christian Ege k423...@gmail.com
mailto:k423...@gmail.com wrote:
Hi,
Hi,
I am building an image for an embedded system using the chiefriver and
kernel 3.12.9. I am using Ubuntu as our base system.
On 02/03/14 12:41, Khem Raj wrote:
There already is a tool called combo-layer to create unified view by
combining layers in OE-Core but its not one of above I think
Awesome! I hadn't noticed that before, thanks for pointing it out.
___
yocto mailing
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto 1.6 status - 10 min (Stephen/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.6_Status
https://wiki.yoctoproject.org/wiki/Yocto_1.6_Features
* SWAT team rotation: Cristian - Laurentiu
Ping ?
2014-01-31 Sébastien Mennetrier s.mennetr...@innotis.org:
Permit to build an image with initramfs.
Signed-off-by: Sébastien Mennetrier s.mennetr...@innotis.org
---
classes/sdcard_image-rpi.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
14 matches
Mail list logo