Hi,
I'm new to Yocto and I've just created a few recipes for my project
(main application and some needed libraries). Now I'd like to create sdk
for my application so it should contain toolchain and the needed
libraries/headers. What should I include in my recipes to get result
like that? I
On 4 June 2014 08:47, Marek Andrus marek.and...@wp.pl wrote:
I believe I'll be able to create the sdk with command like bitbake
my_application -c populate_sdk. I added inherit populate_sdk_base to
my_application.bb. Is that a correct way?
You use -c populate_sdk on an *image* recipe so that
On 4 June 2014 02:03, Lynn 'Cyrin' Conway lynncy...@gmail.com wrote:
-else:
+else:1
Pretty sure you didn't mean that :)
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi
I have a simple recipe (libcec) that I would like to add an additional
configure option to, depending if the machine is an imx6 based one.
How would I do that best?
Here is the recipe:
-
SUMMARY = USB CEC Adaptor communication Library with patches
On 4 June 2014 09:51, Neuer User auslands...@gmx.de wrote:
The conditional configure option is --enable-imx6.
You can use a machine override, along the lines of:
EXTRA_OECONF_ixm6 = --enable-imx6
This will set EXTRA_OECONF to --enable-imx6 if the MACHINE is ixm6.
It gets a little complicated
Hmm, like this?
-
SUMMARY = USB CEC Adaptor communication Library with patches for imx6
HOMEPAGE = http://libcec.pulse-eight.com/;
LICENSE = GPLv2+
LIC_FILES_CHKSUM = file://COPYING;md5=5e8e16396992369f73f3d28875f846da
DEPENDS = udev lockdev
PV = 2.4.1
SRCREV =
The problem is that the MACHINE variable is cubox-i, which is based on
imx6.
Guess that should still work somehow, though...
Am 04.06.2014 11:13, schrieb Neuer User:
Hmm, like this?
-
SUMMARY = USB CEC Adaptor communication Library with patches for imx6
I searched through other recipes for EXTRA_OECONF_ and found somehting
that worked:
EXTRA_OECONF_append_mx6 = --enable-imx6
Main difference is the mx6 versus imx6.
Thanks a lot
Michael
Am 04.06.2014 11:21, schrieb Neuer User:
The problem is that the MACHINE variable is cubox-i, which is
On Monday 02 June 2014 17:26:08 Insop Song wrote:
Thank you very much Paul.
Setting export BB_ENV_EXTRAWHITE=${BUILD_NUMBER} fixed the issue.
I think that should be export BB_ENV_EXTRAWHITE=BUILD_NUMBER (since it's the
variable name you're allowing through, not just the value).
Cheers,
Paul
On 4 June 2014 10:24, Neuer User auslands...@gmx.de wrote:
EXTRA_OECONF_append_mx6 = --enable-imx6
Main difference is the mx6 versus imx6.
Yeah I didn't know what your machine type is, so was guessing.
Ross
--
___
yocto mailing list
On Wednesday 04 June 2014 11:24:36 Neuer User wrote:
I searched through other recipes for EXTRA_OECONF_ and found somehting
that worked:
EXTRA_OECONF_append_mx6 = --enable-imx6
BTW I'd suggest a leading space in the value, since _append won't add one for
you. You might have got away with
Am 04.06.2014 11:59, schrieb Paul Eggleton:
On Wednesday 04 June 2014 11:24:36 Neuer User wrote:
I searched through other recipes for EXTRA_OECONF_ and found somehting
that worked:
EXTRA_OECONF_append_mx6 = --enable-imx6
BTW I'd suggest a leading space in the value, since _append won't add
Hello,
Could you please tell me how to control/select the packages to be
installed in SDK Machine.
For example I have an hmi application based on qt. I can see qmake is
available in ./tmp/sysroots/i686-linux/usr/bin/qt5/qmake at Build host,
but it is not available in sdk machine after
Hi,
I want to capture build history while building an image and I have done the
following settings in conf/local.conf file.
INHERIT += buildhistory
BUILDHISTORY_COMMIT = 1
as suggested in
On Wed, Jun 4, 2014 at 8:35 PM, Bharath Chandra
ellurubharat...@gmail.com wrote:
I want to capture build history while building an image and I have done the
following settings in conf/local.conf file.
INHERIT += buildhistory
BUILDHISTORY_COMMIT = 1
as suggested in
On Wednesday 04 June 2014 20:59:22 Nicolas Dechesne wrote:
On Wed, Jun 4, 2014 at 8:35 PM, Bharath Chandra
ellurubharat...@gmail.com wrote:
I want to capture build history while building an image and I have done
the
following settings in conf/local.conf file.
INHERIT +=
Thank you Paul,
I am new to yocto. I am trying to build the image from scratch again and
now the package folder is generated.
Thanks for the response.
On Wed, Jun 4, 2014 at 4:12 PM, Paul Eggleton paul.eggle...@linux.intel.com
wrote:
On Wednesday 04 June 2014 20:59:22 Nicolas Dechesne
http://autobuilder.yoctoproject.org/pub/nightly/20140603-2
bitbake 18f9bcbad059608e22fca20309314e1c399acec7
eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
eclipse-poky-kepler 984d050eb5aa82d944dcca28c07c07876a36a061
meta-fsl-arm 849e0a68105961f8a02ddd7fb635eb3792e34464
Thank you for the corection Paul, yes you are right.
I actually run the following from jenkins job
export BB_ENV_EXTRAWHITE=BUILD_NUMBER
source SOURCE_THIS
bitbake our_image
On Wed, Jun 4, 2014 at 2:53 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Monday 02 June 2014 17:26:08 Insop
Hi All,
I want include u-boot-fw-utils to my image.
I want to include u-boot-fw-utils_2013.01.01.bb, but
u-boot-fw-utils_2011.06.bb is included if I added it in my image
like following
IMAGE_INSTALL += \
...
u-boot-fw-utils \
Question:
- how to specify bb file when there are multiple
Hi Insop,
Technically u-boot-fw-utils_2013.01.01 should be used because it's the
newer version. However, you can explicitly specify
PREFERRED_VERSION_u-boot-fw-utils = 2013.01.01
Cheers,
Rudi
--
___
yocto mailing list
yocto@yoctoproject.org
Hi Rudi,
Thank you very much for your help.
I've added PREFERRED_VERSION and started build.
Regards,
Insop
On Wed, Jun 4, 2014 at 6:37 PM, Rudolf Streif
rstr...@linuxfoundation.org wrote:
Hi Insop,
Technically u-boot-fw-utils_2013.01.01 should be used because it's the newer
version.
Updates to the arm and i2c
Anders Berg (5):
i2c: axxia: Minor cosmetic cleanup
i2c: axxia: Fall back to polling mode when no IRQ
misc: lsi-smmon: Bug when probing with IRQ pending
misc: lsi-smmon: Add parameter panic_on_fatal
ARM: dts: axxia: Added memory controllers
John Jacques (3):
From: Anders Berg anders.b...@avagotech.com
If the device tree does not specify an interrupt property, the device falls
back to polling the controller status. This is needed to support simulator
models without interrupt capabilities.
Signed-off-by: Anders Berg anders.b...@avagotech.com
---
From: Anders Berg anders.b...@avagotech.com
We must not call the ncr_write function to unmask interrupts with
the memory controller interrupt enabled, as this could cause the ISR to
be invoked before ncr_write has released the lock used to serialize
register accesses.
To avoid this, temporarily
From: Anders Berg anders.b...@avagotech.com
Signed-off-by: Anders Berg anders.b...@avagotech.com
---
arch/arm/boot/dts/axm5516-amarillo.dts |8
arch/arm/boot/dts/axm55xx.dtsi | 14 ++
2 files changed, 22 insertions(+)
diff --git
From: Anders Berg anders.b...@avagotech.com
Added module parameter panic_on_fatal which when set will cause the driver
to call panic() when an uncorrectable ECC error is detected.
Signed-off-by: Anders Berg anders.b...@avagotech.com
---
drivers/misc/lsi-smmon.c | 27
From: John Jacques john.jacq...@lsi.com
The Axxia boot loader leaves secondary cores in reset; Linux is expected
to enable them. This change makes that happen.
Signed-off-by: John Jacques john.jacq...@lsi.com
---
arch/arm/mach-axxia/platsmp.c | 23 ---
1 file changed, 8
From: John Jacques john.jacq...@lsi.com
Add device trees for two new 5500 variants, 5512 and 5508.
Signed-off-by: John Jacques john.jacq...@lsi.com
---
arch/arm/boot/dts/Makefile |4 +-
arch/arm/boot/dts/axm5508-amarillo.dts | 221
29 matches
Mail list logo
