Am 15.05.2014 22:43, schrieb Richard Purdie:
On Wed, 2014-05-14 at 16:42 +0200, Neuer User wrote:
Probably solved. It should be
include conf/distro/poky.conf
instead of
include poky.conf.
(Stupid newbie error).
FWIW if you said require instead of include you'd have got a useful
error
Hi Ash,
On Thursday 15 May 2014 21:41:55 Ash Charles wrote:
Under what conditions can I change the content of layers without
affecting an ongoing bitbake?
On occasion, I find myself wanting to do git operations on my layers
while I've got a build going on. I've typically assumed this might
On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
On 13/05/2014 14:56, Robert P. J. Day wrote:
On Tue, 29 Apr 2014, Alex J Lennon wrote:
On 29/04/2014 17:34, Robert P. J. Day wrote:
i've just been asked to design a linux device drivers course based
on the arduino-compatible intel
On 16/05/2014 11:11, Paul Eggleton wrote:
On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
On 13/05/2014 14:56, Robert P. J. Day wrote:
On Tue, 29 Apr 2014, Alex J Lennon wrote:
On 29/04/2014 17:34, Robert P. J. Day wrote:
i've just been asked to design a linux device drivers course
On Friday 16 May 2014 11:29:34 Alex J Lennon wrote:
On 16/05/2014 11:11, Paul Eggleton wrote:
On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
On 13/05/2014 14:56, Robert P. J. Day wrote:
On Tue, 29 Apr 2014, Alex J Lennon wrote:
On 29/04/2014 17:34, Robert P. J. Day wrote:
i've
On 2014-05-15 14:53, Richard Purdie wrote:
On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
I have a number of platforms which [for whatever reason]
need older versions of GCC. I've been supporting this by
keeping the older code around in my own layers - I need
4.7.x for some targets,
Hi Gary,
On Friday 16 May 2014 04:50:47 Gary Thomas wrote:
On 2014-05-15 14:53, Richard Purdie wrote:
On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
I have a number of platforms which [for whatever reason]
need older versions of GCC. I've been supporting this by
keeping the older
I think you should probably have meta-iot-devkit as well even if you don't
use
DISTRO = iot-devkit.
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:
Hello
I am trying to build a simple recipe for a package called pyotherside.
It currently looks like this:
SUMMARY = Python3 bindings for Qt5
DESCRIPTION = New framework for including pyhton interpreter into Qt5 apps
On 2014-05-16 05:16, Paul Eggleton wrote:
Hi Gary,
On Friday 16 May 2014 04:50:47 Gary Thomas wrote:
On 2014-05-15 14:53, Richard Purdie wrote:
On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
I have a number of platforms which [for whatever reason]
need older versions of GCC. I've
On Friday 16 May 2014 12:17:33 Alex J Lennon wrote:
I think you should probably have meta-iot-devkit as well even if you don't
use DISTRO = iot-devkit.
I added meta-iot-devkit in to bblayers and when I bitbake
iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned
bbappends.
On Fri, 16 May 2014, Paul Eggleton wrote:
... snip ...
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 images for Galileo using what's in
* Neuer User auslands...@gmx.de [140516 13:24]:
require recipes-qt/qt5/qt5.inc
It is WIP, so e.g. the license is stil wrong.
The package depends on Qt5 and Python3.
In that case, I would have expected to see
On 16/05/2014 12:32, Paul Eggleton wrote:
On Friday 16 May 2014 12:17:33 Alex J Lennon wrote:
I think you should probably have meta-iot-devkit as well even if you don't
use DISTRO = iot-devkit.
I added meta-iot-devkit in to bblayers and when I bitbake
iot-devkit-image (MACHINE=clanton,
Am 16.05.2014 14:04, schrieb Anders Darander:
* Neuer User auslands...@gmx.de [140516 13:24]:
require recipes-qt/qt5/qt5.inc
It is WIP, so e.g. the license is stil wrong.
The package depends on Qt5 and Python3.
Am 16.05.2014 14:16, schrieb Neuer User:
Am 16.05.2014 14:04, schrieb Anders Darander:
Great, that helped with no 1.). Still a lot to learn for me.
No 2. is still open, though. Is that a problem of my recipe or rather a
generic problem of the python3 recipe? I could patch the python3
On Friday 16 May 2014 05:31:41 Gary Thomas wrote:
On 2014-05-16 05:16, Paul Eggleton wrote:
On Friday 16 May 2014 04:50:47 Gary Thomas wrote:
On 2014-05-15 14:53, Richard Purdie wrote:
On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
I have a number of platforms which [for whatever
On Fri, 16 May 2014, Paul Eggleton wrote:
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
images for Galileo using what's in
On Friday 16 May 2014 08:51:35 Robert P. J. Day wrote:
On Fri, 16 May 2014, Paul Eggleton wrote:
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
On Friday 16 May 2014 07:37:01 Robert P. J. Day wrote:
On Fri, 16 May 2014, Paul Eggleton wrote:
... snip ...
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
On Fri, 16 May 2014, Paul Eggleton wrote:
On Friday 16 May 2014 08:51:35 Robert P. J. Day wrote:
On Fri, 16 May 2014, Paul Eggleton wrote:
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
--- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg
+++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg
@@ -1,4 +1,4 @@
CONFIG_STAGING=y
CONFIG_WATCHDOG_CORE=y
CONFIG_INTEL_MEI=y
The CONFIG_INTEL_MEI also need to be converted to module.
I realize that there is no
On 2014-05-16 06:42, Paul Eggleton wrote:
On Friday 16 May 2014 05:31:41 Gary Thomas wrote:
On 2014-05-16 05:16, Paul Eggleton wrote:
On Friday 16 May 2014 04:50:47 Gary Thomas wrote:
On 2014-05-15 14:53, Richard Purdie wrote:
On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
I have a
Ok, so looking at this a bit more and I think we need to look at how
we set up the deploydir in PublishArtifacts a bit more.
I think what we can do here is pull the functionality that we have in
getDeployNames out, and put it into GetDeployDir (layerversion here
matters as the default deploy for
On Fri, May 16, 2014 at 5:33 AM, Neuer User auslands...@gmx.de wrote:
If I change the sed line to #!/usr/bin/env python3, that would
probably work then. But would it break something else?
would be fine.
--
___
yocto mailing list
On Fri, May 16, 2014 at 10:11 AM, Gary Thomas g...@mlbassoc.com wrote:
On 2014-05-16 06:42, Paul Eggleton wrote:
On Friday 16 May 2014 05:31:41 Gary Thomas wrote:
On 2014-05-16 05:16, Paul Eggleton wrote:
On Friday 16 May 2014 04:50:47 Gary Thomas wrote:
On 2014-05-15 14:53, Richard
On 5/16/2014 6:58 AM, Ong, Boon Leong wrote:
--- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg
+++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg
@@ -1,4 +1,4 @@
CONFIG_STAGING=y
CONFIG_WATCHDOG_CORE=y
CONFIG_INTEL_MEI=y
The CONFIG_INTEL_MEI also need to be converted to module.
27 matches
Mail list logo
