yocto@lists.yoctoproject.org

Re: Recipe differences between Danny and Master

You don't need to specify the myaudios-1.0 section, that's implicit in the search paths along with the unversioned ${BPN} and files/. SRC_URI="file://myaudios-1.0.tar.gz" will find it and also work

By Burton, Ross <ross.burton@...> · #11152 ·

[PATCH 5/5] scripts/lib/bsp/engine.py: refactor bsp-creation code

From: Tom Zanussi <tom.zanussi@...> This does a bit of refactoring of the bsp-generation code to make it generically reusable for generating non-bsp layers. The first user remains the existing

By tom.zanussi@... · #11149 ·

[PATCH 4/5] yocto-layer: add 'layer' template data

From: Tom Zanussi <tom.zanussi@...> Add a 'layer' target containing all the data that will be used to generate a generic yocto layer. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---

By tom.zanussi@... · #11148 ·

[PATCH 3/5] yocto-layer: add help/usage

From: Tom Zanussi <tom.zanussi@...> This is essentially 'the documentation' for the yocto-layer tool. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- scripts/lib/bsp/help.py | 228

By tom.zanussi@... · #11147 ·

[PATCH 0/5] RFC: new 'yocto-layer' tool for creating generic Yocto layers

From: Tom Zanussi <tom.zanussi@...> Since I've been doing kind of similar work lately for the 'custom kernel' support for yocto-bsp and have gotten several requests lately (mainly from Darren

By tom.zanussi@... · #11150 ·

[PATCH 2/5] yocto-layer: new script

From: Tom Zanussi <tom.zanussi@...> Implementation of the 'yocto-layer' command-line tool, for creating generic layers and listing their input properties. Signed-off-by: Tom Zanussi

By tom.zanussi@... · #11151 ·

[PATCH 1/5] scripts/lib/bsp/engine.py: add yocto_layer_create()

From: Tom Zanussi <tom.zanussi@...> Add a new yocto_layer_create() function that will be used to generate a generic yocto layer (for the new 'yocto-layer' command). Signed-off-by: Tom Zanussi

By tom.zanussi@... · #11146 ·

Recipe differences between Danny and Master

I have a recipe layers I use for test videos and audios that I included in prior BSPs I've done. The last I tested it was Danny and it worked fine. Today I tried to add it to a BSP that had

By Jim Abernathy · #11145 ·

Re: Specifying different make flags for different tasks.

Hi Chris, Yes, that would be exactly what I want, except that it' not working for me. Probably something obvious, but just in case, any reason why this should not work in denzil? Thanks, Alex

By Alex Gonzalez · #11144 ·

Re: IMHO, cross-compile/toolchain examples should use non-x86 arches

Or in Yocto Project context, we kind of use ADT more inclusive that referring what Mark talked about SDK, the eclipse plug-in and other developers tools. And we don't call out SDK that much.

By Zhang, Jessica · #11143 ·

Re: IMHO, cross-compile/toolchain examples should use non-x86 arches

The biggest clarify problem I've seen is the terms being intermingled. There are clear definitions for each. Toolchain, the compiler and related tools that enable compiling software for a given

By Mark Hatle <mark.hatle@...> · #11142 ·

Re: Where does the bitbake get the variable "TOPDIR"

It's defind in "lib/bb/parse/parse_py/ConfHandler.py:36". When TOPDIR is not defined in any of the bitbake configuration files, it's set to current working directory automatically. (...) def

By Eren Türkay <eren@...> · #11141 ·

Re: Specifying different make flags for different tasks.

On Mon, Dec 17, 2012 at 1:36 AM, Alex Gonzalez <alex@...> wrote: I am using EXTRA_OEMAKE to pass extra flags to make. How can I pass different flags for different tasks? In this case I am compiling

By Chris Larson <clarson@...> · #11140 ·

Re: libva failing for mp4 using gstreamer under 'danny' with cedartrail BSP

Hi Ross, One question - is that also true for 'fakesink'? I thought that was supposed to accept any format, but it also throws the same error. My pipeline is just uridecodebin ! fakesink Chris

By Chris Tapp · #11139 ·

[PATCH] Added ability to parse python sources to create-recipe

Hi, Added python source parsing abilities to create-recipe. Signed-off-by: David Nyström <david.nystrom@...> --- scripts/create-recipe | 51

By "David Nyström <david.c.nystrom@...> · #11138 ·

Re: Where does the bitbake get the variable "TOPDIR"

Now i got it. Bitbake handles the variable TOPDIR, LAYERDIR internally. Thanks anyway, Biao

By Biao <huanmateme@...> · #11137 ·

Where does the bitbake get the variable "TOPDIR"

Greetings, I am a newbie tying to understand how bitbake works. There is one line as BBPATH = "${TOPDIR}" in the mybuild/conf/bblayers.conf, i would like to know where the TOPDIR is defined?

By Biao <huanmateme@...> · #11136 ·

Specifying different make flags for different tasks.

Hi, I am using EXTRA_OEMAKE to pass extra flags to make. How can I pass different flags for different tasks? In this case I am compiling an external kernel module and I need different make flags

By Alex Gonzalez · #11135 ·

Re: IMHO, cross-compile/toolchain examples should use non-x86 arches

My 2c (USD) is for clarity on ADT vs. SDK vs. Toolchain. Regards, Sean Liming Owner Annabooks Tel: 714-970-7523 / Cell: 858-774-3176

By Sean Liming <sean.liming@...> · #11134 ·

IMHO, cross-compile/toolchain examples should use non-x86 arches

a general preference on my part, but i think it would be useful if any yocto docs that are discussing toolchains or cross-compilation or the like use *non*-x86 architectures to get the point across.

By Robert P. J. Day · #11133 ·

Messages