Good day ALL,
I was wondering if it's possible to automatically add QEMU dependencies
(kernel and ext3 files) into the script generated by do_populate_sdk? Then
after running the generated SDK script, the images will reside in
/path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an environment
I have run below command
bitbake -c fetchall core-image-minimal
It has created downloads directory and packages source codes are
there inside, but i am not able to find the kernel and u-boot source code.
I have build core-image-minimal without internet connectivity, and kernel and
u-boot have al
Good day ALL,
I was wondering if it's possible to automatically add QEMU dependencies
(kernel and ext3 files) into the script generated by do_populate_sdk? Then
after running the generated SDK script, the images will reside in
/path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an environment
Also look into the buildhistory class.
Philip
On 07/07/2014 12:26 PM, Alexandru Vaduva wrote:
> using:
>
> bitbake -g && cat pn-depends.dot | grep -v -e '-native' | grep
> -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq
>
> you can visualize the image packages. Let me know i
Hi Atul,
On Tue, Jul 08, 2014 at 12:41:22AM +0530, atulkumar singh wrote:
> Hi All,
>
> Is there support for Aarch64(64 bit ARMv8) available right now?
Yes. Aarch64 support is available in meta-linaro/meta-aarch64
URL: http://git.linaro.org/?p=openembedded/meta-linaro.git
> If so then what i nee
Hi All,
Is there support for Aarch64(64 bit ARMv8) available right now?
If so then what i need to mention as a MACHINE in local.conf.
Please let me know with your valuable suggestion if any.
Thanks and regards,
Atul
--
___
yocto mailing list
yocto@yoct
Gary,
On Mon, Jul 7, 2014 at 11:02 AM, Gary Thomas wrote:
> The big thing missing from this version(*) is no cape support,
> so if you need an LCD display or CAN driver or ..., you're not
> going to find it. The meta-ti version does support those AFAIK
>
> (*) unless this changed in the last t
Hello Jeff,
The errors are package related.
Meta-cgl can be seen as a non BSP specific layer (it can be viewed as the LSB
from poky).
I already started fixing a number, of the already existing errors and the
patches will be added upstream after proper testing.
I will continue the bug fixing and
using:
bitbake -g && cat pn-depends.dot | grep -v -e '-native' | grep -v
digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq
you can visualize the image packages. Let me know if this is what you are
looking for.
On Monday, July 7, 2014 7:04 PM, Bharath Chandra
wrote:
Hi All
Hi All,
I have an image deployed on gumstix board and I do not know the recipe file
used to build that image. I want to know list of recipes used to build that
image. Is it possible??
Thanks & Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.
--
__
On 2014-07-07 07:33, Robert P. J. Day wrote:
On Mon, 7 Jul 2014, Bruce Ashfield wrote:
On 14-07-07 09:13 AM, Robert P. J. Day wrote:
i want to build a bootable system for a BBB, and i can see at least
three possibilities:
1) the meta-yocto-bsp layer defines the beaglebone as one of i
On Mon, 7 Jul 2014, Bruce Ashfield wrote:
> On 14-07-07 09:13 AM, Robert P. J. Day wrote:
> >
> >i want to build a bootable system for a BBB, and i can see at least
> > three possibilities:
> >
> >1) the meta-yocto-bsp layer defines the beaglebone as one of its
> > reference boards
>
On 14-07-07 09:13 AM, Robert P. J. Day wrote:
i want to build a bootable system for a BBB, and i can see at least
three possibilities:
1) the meta-yocto-bsp layer defines the beaglebone as one of its
reference boards
2) the "meta-ti" layer is advertised as "official" TI board su
Use the branch in refs/head instead of the tag.
This allows a given tag name to differ from the branch name.
Signed-off-by: Richard Leitner
---
bitbake/lib/bb/fetch2/git.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bitbake/lib/bb/fetch2/git.py b/bitbake/lib/bb/fetch2
Hi folks,
I've ran into a problem using tag names in SRCREV for git repositories after
migrating from 1.4 to 1.6.1 "daisy".
Before (1.4) the following worked fine:
SRCREV = "v${PV}"
SRC_URI = "git://github.com/rleitner/psplash.git;protocol=https"
When using 1.6.1 the following er
i want to build a bootable system for a BBB, and i can see at least
three possibilities:
1) the meta-yocto-bsp layer defines the beaglebone as one of its
reference boards
2) the "meta-ti" layer is advertised as "official" TI board support
3) there is a "meta-beagleboard" layer, but
perusing dev manual and section 5.17.1:
IMAGE_FEATURES = "read-only-rootfs"
or
EXTRA_IMAGE_FEATURES += "read-only-rootfs"
um ... isn't that backwards? should you not be appending to
IMAGE_FEATURES, but simply setting EXTRA_IMAGE_FEATURES? or have i
already forgotten how that works?
Hi Nicolas/Sathish,
Thank you both very much for your responses. With your help, I have been able
to copy the pre-compiled libraries to my image now.
Cheers,
Josh
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo
Hi,
While upgrading poky daisy branch to YPv1.6.1, both Brendan & I observed
that there is an circular dependency issue in initscripts.
Strangely, this issue is not observable if we are building poky as it is,
but is observable when we use it together with meta-intel-iot-devkit.
We h
On Fri, Jul 4, 2014 at 9:37 AM, Joshua Collins
wrote:
> This does not copy the files to the image as I would expect. If I look at
> the bitbake log, I see my recipe is run, but I obviously have not done the
> right thing in the recipe.
>
>
>
> Can anyone tell me how I could fix this?
.so files ar
Hi Josh,
Try adding the following to your myrecipe.bb
FILES_${PN} += "${libdir} /etc"
FILES_${PN}-dbg += "${libdir}/.debug /etc/.debug"
FILES_SOLIBSDEV = ""
Note:
Try following if any issue
FILES_${PN}-dbg += "${libdir}/.debug"
Regards,
B.Sathish Kumar
From: yocto-boun...@yoctoproject.org [mai
21 matches
Mail list logo
