| Summary: | Suggested documentation for the currently undocumented *_task-foo override syntax | ||
|---|---|---|---|
| Product: | [Documentation] BitBake User Manual | Reporter: | ulfalizer |
| Component: | bitbake-manual | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, richard.purdie, srifenbark |
| Version: | 2.2 | ||
| Target Milestone: | 2.3 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 10 April 2017: RESOLVED | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Done (doc changes complete) | |
Ulf, See http://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual.html#conditional-metadata for the new item in that list. Scott One nit: The "e.g." before "_prepend" got lost in This syntax can also be combined with "_prepend" Without it, it sounds like it can only be combined with "_prepend" and not e.g. "_append". Cheers, Ulf (In reply to comment #2) > One nit: The "e.g." before "_prepend" got lost in > > This syntax can also be combined with "_prepend" > > Without it, it sounds like it can only be combined with "_prepend" and not > e.g. "_append". Look at this version - http://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual.html#conditional-metadata. I didn't like the way it originally read. Will this work? > > Cheers, > Ulf (In reply to comment #3) > (In reply to comment #2) > > One nit: The "e.g." before "_prepend" got lost in > > > > This syntax can also be combined with "_prepend" > > > > Without it, it sounds like it can only be combined with "_prepend" and not > > e.g. "_append". > > Look at this version - > http://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual. > html#conditional-metadata. I didn't like the way it originally read. Will > this work? Looks good to me. I agree that "this syntax can also be combined with for example..." sounds a bit sloppy. :) Cheers, Ulf Great, I was just about to file this. One note to make is that if the task name contains underscores then they need to be replaced with hyphens when specifying the override e.g. VARNAME_task-populate-sysroot = "somevalue" Moving to 2.3 M2 Setting to 2.3 M4. Paul - See http://www.yoctoproject.org/docs/2.3/bitbake-user-manual/bitbake-user-manual.html#conditional-metadata and the "Setting a Variable for a Single Task" item in the list. I added a new note. Tell me if this is okay. Thanks, Scott Hi, No review since March 20th... assuming okay. Setting to RESOLVED and marking the doc flag "done." Scott |
There's a FOO_task-mytask override syntax that sets a variable just for the duration of a single task, but it's currently undocumented. I suggest adding a new entry to the end of '3.2.1. Conditional Metadata': * Setting a variable for a single task: BitBake supports setting a variable just for the duration of a single task. Here is an example: FOO_task-configure = "val 1" FOO_task-compile = "val 2" In this example, FOO will have the value "val 1" while the do_configure task is executed, and the value "val 2" while the do_compile task is executed. Internally, this is implemented by prepending e.g. "task-compile:" to the value of OVERRIDES for the local datastore of the do_compile task. This syntax can also be combined with e.g. "_prepend", as in the following example: EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} " Cheers, Ulf