[yocto] 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 for the do_make_scripts and do_compile tasks. If I set EXTRA_OEMAKE in the recipe, all tasks use the

[yocto] 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? Thanks, Biao___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] Where does the bitbake get the variable TOPDIR

Now i got it. Bitbake handles the variable TOPDIR, LAYERDIR internally. Thanks anyway, Biao At 2012-12-17 17:06:26,Biao huanmat...@163.com wrote: 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

[yocto] [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.nyst...@enea.com --- scripts/create-recipe | 51 ++--- 1 file changed, 48 insertions(+), 3 deletions(-) diff --git a/scripts/create-recipe

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

Hi Ross, On 13 Dec 2012, at 23:58, Burton, Ross wrote: On 13 December 2012 23:23, Chris Tapp opensou...@keylevel.com wrote: Unfortunately, adding xvimagesink hasn't helped. I also still don't really understand why webm and flv work ok. They're probably using ximagesink, but depending on

Re: [yocto] Specifying different make flags for different tasks.

On Mon, Dec 17, 2012 at 1:36 AM, Alex Gonzalez a...@lindusembedded.comwrote: 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 for the do_make_scripts

Re: [yocto] Where does the bitbake get the variable TOPDIR

On Mon, Dec 17, 2012 at 05:06:26PM +0800, Biao wrote: 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? It's defind in

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

On 12/16/12 4:57 PM, Sean Liming wrote: My 2c (USD) is for clarity on ADT vs. SDK vs. Toolchain. 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

Re: [yocto] 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. --Jessica -Original Message- From: yocto-boun...@yoctoproject.org

Re: [yocto] 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 On Mon, Dec 17, 2012 at 4:24 PM, Chris Larson clar...@kergoth.com wrote: On Mon, Dec 17, 2012 at

[yocto] Recipe differences between Danny and Master

= nuc DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20121217 TUNE_FEATURES = m64 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:958162e96b4a4f23bca94500b5f20975633dd5c6 meta-intel meta-nuc = master:4122c514a22442a58b2f99e4ba9617ff219b3089 meta-jfa

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

From: Tom Zanussi tom.zanu...@intel.com 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 tom.zanu...@intel.com --- scripts/lib/bsp/engine.py | 56

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

From: Tom Zanussi tom.zanu...@intel.com This is essentially 'the documentation' for the yocto-layer tool. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- scripts/lib/bsp/help.py | 228 1 file changed, 228 insertions(+) diff --git

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

From: Tom Zanussi tom.zanu...@intel.com Add a 'layer' target containing all the data that will be used to generate a generic yocto layer. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- .../bsp/substrate/target/arch/layer/COPYING.MIT| 17 ++

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

From: Tom Zanussi tom.zanu...@intel.com 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 yocto-bsp tool; these changes allow a second user, the new yocto-layer tool, to use the same code.

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

From: Tom Zanussi tom.zanu...@intel.com 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 in support of the new kernel documentation) for something like this, I decided to just go ahead and

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

From: Tom Zanussi tom.zanu...@intel.com Implementation of the 'yocto-layer' command-line tool, for creating generic layers and listing their input properties. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- scripts/yocto-layer | 142 1

Re: [yocto] Recipe differences between Danny and Master

On 17 December 2012 17:45, Jim Abernathy jfaberna...@gmail.com wrote: SRC_URI = file://myaudios-1.0/myaudios-1.0.tar.gz 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

[yocto] Error: nativesdk-qemu-helper_1.0.bb, do_compile, for gcc-4.5.4 and eglibc-2.13 port against current poky master

Hi, While attempting to maintain the gcc-4.5.4 and eglibc-2.13 recipes, against the current poky master, I ran into the following errors, while running bitbake meta-toolchain: ERROR: Function failed: do_compile (see

[yocto] ERROR: locale-base-tt-ru is listed in PACKAGES multiple times, this leads to packaging errors.

Hi, While attempting to maintain the gcc-4.5.4 and eglibc-2.13 recipes, against the current poky master, I ran into the following errors, while running bitbake meta-toolchain: ERROR: locale-base-tt-ru is listed in PACKAGES multiple times, this leads to packaging errors. How can I fix

Re: [yocto] Recipe differences between Danny and Master

On 12/17/2012 12:55 PM, Burton, Ross wrote: On 17 December 2012 17:45, Jim Abernathy jfaberna...@gmail.com wrote: SRC_URI = file://myaudios-1.0/myaudios-1.0.tar.gz You don't need to specify the myaudios-1.0 section, that's implicit in the search paths along with the unversioned ${BPN} and

[yocto] experimental/meta-tpm replaced by experimental/meta-trusted

The public git repository experimental/meta-tpm has been replaced with experimental/meta-trusted which will include libraries and tools that are not necessarily TCG/TPM destined as well as the work that was already in place. Find the new repository at

Re: [yocto] bitbake user manual vs mega manual, and more info on local file fetcher?

Hi, I'm glad to hear that the bitbake manual is getting an update, and I'm sure you guys know a lot of debugging tricks that I don't know. Can you please include a section on debugging bitbake build errors (beyond logs, -D, and -v)? In other words, what's the best way to instrument or hack

Re: [yocto] [PATCH runqemu] runqemu: add support for FSTYPE=vmdk

On 12/15/2012 04:18 AM, Trevor Woerner wrote: Is there a chance this can get included? I believe a rebase is needed and please sent to oe-core mailing list. Thanks Sau! ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] Git tag systematics ?

In message 20121215132238.503dc201...@gemini.denx.de I wrote: Hi, can anybody explain to me the systematics of the git tags ysed to mark the Yocto / Poky releases? For example, for Yocto 1.2 and before, we have release tags like denzil-7.0, edison-6.0, bernard-5.0, laverne-4.0, etc.