Hello,
what is the contents of
custom-image-zedboard-20131214212545.rootfs.ext2.gz.u-boot. How do
transfer to mmc?
What files are needed from the deploy/images to boot a zedboard?
Thanks
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctopr
Everyone‹
I¹m not sure where is the best place to take this question. Please excuse
me, I¹m new.
I¹m struggling to build an OS X toolchain reliably and repeatably. I¹ve
checked out the current top of the Œdylan¹ branch of Poky, meta-darwin,
meta-intel and (for reasons I¹m not sure I understand)
On Fri, Dec 20, 2013 at 10:11:43AM +, Brad Litterell wrote:
> Hi again,
> Is it possible I don't have sigdata files?
>
> I am trying bitbake-diffsigs -t
>
> For recipe, I've tried the package name: "etm-core" & file name "etm-core.bb"
> for task, I've tried fetch, configure, compile, inst
Hi again,
Is it possible I don't have sigdata files?
I am trying bitbake-diffsigs -t
For recipe, I've tried the package name: "etm-core" & file name "etm-core.bb"
for task, I've tried fetch, configure, compile, install, do_install.
All come back with same message "no sigdata files found matc
I'll have a look at diffsigs. ${ETM_DEBUG} is the parsed representation of
just the debug flag in MY_FEATURES (assuming I'll have more than one flag in
MY_FEATURES eventually). So, in this case, yes they are referring to the same.
Thanks for asking though.
___
On Fri, Dec 20, 2013 at 09:39:13AM +, Brad Litterell wrote:
> I'm using it in a task, like this:
> do_install_prepend() {
> if [ ! -z ${ETM_DEBUG} ]; then
> ...do debugging stuff ...
> fi
> }
>
> but having it in a task definition doesn't seem to taint the sstate. Trying
>
I'm using it in a task, like this:
do_install_prepend() {
if [ ! -z ${ETM_DEBUG} ]; then
...do debugging stuff ...
fi
}
but having it in a task definition doesn't seem to taint the sstate. Trying to
figure out what other variables go into it. E.g. does DESCRIPTION get included
On Fri, Dec 20, 2013 at 03:09:31AM +, Brad Litterell wrote:
> Hi Martin,
>
> I decided just to create my own feature list:
>
> MY_FEATURES="debug"
>
> and I can happily query it in my custom recipes.
>
> However, I haven't quite figured out the best way to taint the status hashes
> for my
I am having trouble getting my build environment to work offline. I followed
the instructions here:
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F
I've built my project, created the tarballs, etc. However, it appears there is
still something I'
