|
Re: can one lay hands on a galileo-based dev kit?
Are you trying to use these layers with 1.6 / master? Until the devkit-daisy
branch was pushed, the devkit was based on 1.5 (dora).
If you get this error, it means there is a grub recipe but no
Are you trying to use these layers with 1.6 / master? Until the devkit-daisy
branch was pushed, the devkit was based on 1.5 (dora).
If you get this error, it means there is a grub recipe but no
|
By
Paul Eggleton
·
#19655
·
|
|
Re: Where did my preferred version go?
I looked back through this thread and the enhancement bug I filed
(which for everyone but Richard seemed to be the way to go). The
result was to reuse sstate, but I don't see how that can solve
I looked back through this thread and the enhancement bug I filed
(which for everyone but Richard seemed to be the way to go). The
result was to reuse sstate, but I don't see how that can solve
|
By
Gary Thomas
·
#19654
·
|
|
Help with building app recipe
Hello
I am trying to build a simple recipe for a package called "pyotherside".
It currently looks like this:
------------------------------------------------------------------------
SUMMARY =
Hello
I am trying to build a simple recipe for a package called "pyotherside".
It currently looks like this:
------------------------------------------------------------------------
SUMMARY =
|
By
Neuer User <auslands-kv@...>
·
#19653
·
|
|
Re: can one lay hands on a galileo-based dev kit?
I added meta-iot-devkit in to bblayers and when I bitbake
iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned
bbappends.
ERROR: No recipes available for:
I added meta-iot-devkit in to bblayers and when I bitbake
iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned
bbappends.
ERROR: No recipes available for:
|
By
Alex J Lennon <ajlennon@...>
·
#19652
·
|
|
Re: Where did my preferred version go?
Hi Gary,
We don't support this usage at the moment in OE; if you use the OE toolchain
we recommend you let the system build it, and it will then be restored from
shared state for subsequent builds.
Hi Gary,
We don't support this usage at the moment in OE; if you use the OE toolchain
we recommend you let the system build it, and it will then be restored from
shared state for subsequent builds.
|
By
Paul Eggleton
·
#19651
·
|
|
Re: Where did my preferred version go?
I made a complete copy of recipes-devtools/gcc before the original 4.8
recipes were added.
Thanks for these pointers. I've given them a quick look and indeed
they look manageable, so I'll probably
I made a complete copy of recipes-devtools/gcc before the original 4.8
recipes were added.
Thanks for these pointers. I've given them a quick look and indeed
they look manageable, so I'll probably
|
By
Gary Thomas
·
#19650
·
|
|
Re: can one lay hands on a galileo-based dev kit?
I think you should probably have meta-iot-devkit as well even if you don't use
DISTRO = "iot-devkit".
When you say "missing grub" can you be more specific about the error?
Well, looking at the
I think you should probably have meta-iot-devkit as well even if you don't use
DISTRO = "iot-devkit".
When you say "missing grub" can you be more specific about the error?
Well, looking at the
|
By
Paul Eggleton
·
#19649
·
|
|
Re: can one lay hands on a galileo-based dev kit?
Thanks Paul. Very useful, particularly the image creation incantations.
I'll give this a go as soon as I can make some time.
I really want to be building the same distro for multiple targets
Thanks Paul. Very useful, particularly the image creation incantations.
I'll give this a go as soon as I can make some time.
I really want to be building the same distro for multiple targets
|
By
Alex J Lennon <ajlennon@...>
·
#19648
·
|
|
Re: can one lay hands on a galileo-based dev kit?
So apologies for not replying earlier - I've not been directly involved in the
BSP for Galileo, but I have been providing support for the team doing the IoT
DevKit work. You should be able to build
So apologies for not replying earlier - I've not been directly involved in the
BSP for Galileo, but I have been providing support for the team doing the IoT
DevKit work. You should be able to build
|
By
Paul Eggleton
·
#19647
·
|
|
Re: Changing metadata during bitbaking
Hi Ash,
That's pretty much what I follow, although I try to avoid modifying recipes at
all while there's a chance they might be built - recipes *do* get re-parsed
during execution, not just when
Hi Ash,
That's pretty much what I follow, although I try to avoid modifying recipes at
all while there's a chance they might be built - recipes *do* get re-parsed
during execution, not just when
|
By
Paul Eggleton
·
#19646
·
|
|
Re: Best way to remove DISTRO_FEATURES?
Am 15.05.2014 22:43, schrieb Richard Purdie:
Ah, really? So, "include" means, "if you find it then include it - if
not, then doesn't matter"?
Good to know :-)
Thanks to everybody. I have it working
Am 15.05.2014 22:43, schrieb Richard Purdie:
Ah, really? So, "include" means, "if you find it then include it - if
not, then doesn't matter"?
Good to know :-)
Thanks to everybody. I have it working
|
By
Neuer User <auslands-kv@...>
·
#19645
·
|
|
Changing metadata during bitbaking
Hi,
(apologies if this is the wrong list---I tried sending to the bitbake
list and got bounced)
Under what conditions can I change the content of layers without
affecting an ongoing bitbake?
On
Hi,
(apologies if this is the wrong list---I tried sending to the bitbake
list and got bounced)
Under what conditions can I change the content of layers without
affecting an ongoing bitbake?
On
|
By
Ash Charles <ashcharles@...>
·
#19644
·
|
|
[PATCH 9/9] Use wildcard in glib-2.0 bbappend name
glib-2.0: Update to match version in Poky
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/glib-2.0/glib-2.0_2.%.bbappend | 1 +
recipes-core/glib-2.0/glib-2.0_2.38.2.bbappend
glib-2.0: Update to match version in Poky
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/glib-2.0/glib-2.0_2.%.bbappend | 1 +
recipes-core/glib-2.0/glib-2.0_2.38.2.bbappend
|
By
Armin Kuster
·
#19643
·
|
|
[PATCH 8/9] update psmics 22.21 and remove unneeded patch
psmics: Update to match version in Poky and remove patch.
Signed-off-by: Armin Kuster <akuster808@...>
---
.../psmisc/pstree-compiles-with-SE-Linux.patch | 265 ---------------------
psmics: Update to match version in Poky and remove patch.
Signed-off-by: Armin Kuster <akuster808@...>
---
.../psmisc/pstree-compiles-with-SE-Linux.patch | 265 ---------------------
|
By
Armin Kuster
·
#19642
·
|
|
[PATCH 7/9] Update to latest swig from meta-openembedded
swig: Update to latest swig from meta-openembedded
Updated from:
git://git.openembedded.org/meta-openembedded/meta-oe/recipes-devtools/swig
As of commit
swig: Update to latest swig from meta-openembedded
Updated from:
git://git.openembedded.org/meta-openembedded/meta-oe/recipes-devtools/swig
As of commit
|
By
Armin Kuster
·
#19641
·
|
|
[PATCH 6/9] update util-linux package version and remove patch
util-linux: Update package to match Poky master.
Remove patch since it was merged upstream.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/util-linux/util-linux_2.23.2.bbappend
util-linux: Update package to match Poky master.
Remove patch since it was merged upstream.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/util-linux/util-linux_2.23.2.bbappend
|
By
Armin Kuster
·
#19640
·
|
|
[PATCH 5/9] Use wildcard in openssh name
openssh: Use wildcard in version to minimize keeping in-sync with Poky
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/openssh/openssh_6.%.bbappend | 11 +++++++++++
openssh: Use wildcard in version to minimize keeping in-sync with Poky
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/openssh/openssh_6.%.bbappend | 11 +++++++++++
|
By
Armin Kuster
·
#19638
·
|
|
[PATCH 4/9] Use wildcard in kernel bbappend name
linux-kernel: Use wildcard in version to minimize keeping in-sync with Poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-kernel/linux/linux-yocto_3.%.bbappend | 7 +++++++
linux-kernel: Use wildcard in version to minimize keeping in-sync with Poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-kernel/linux/linux-yocto_3.%.bbappend | 7 +++++++
|
By
Armin Kuster
·
#19639
·
|
|
[PATCH 3/9] Use wildcard in bind bbappend name
bind: Use wildcard to minimize the need to keep tp keep in-synx
with Poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/bind/bind_9.%.bbappend | 2 --
1 file
bind: Use wildcard to minimize the need to keep tp keep in-synx
with Poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/bind/bind_9.%.bbappend | 2 --
1 file
|
By
Armin Kuster
·
#19637
·
|
|
[PATCH 2/9] Use wildcard in bind bbappend name
bind: Use wildcard to minimize the need to keep in-sync
with poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/bind/bind_9.%.bbappend | 13 +++++++++++++
bind: Use wildcard to minimize the need to keep in-sync
with poky.
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-connectivity/bind/bind_9.%.bbappend | 13 +++++++++++++
|
By
Armin Kuster
·
#19636
·
|