From 72d1435f20e47339c75ee8dcb8adecbb2bc7516b Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 7 Sep 2016 10:17:42 -0700 Subject: documentation: Added new description for the PACKAGECONFIG_CONFARGS variable. Fixes [YOCTO #10183] Added a new variable entry for the PACKAGECONFIG_CONFARGS variable. With the introduction of the new PACKAGECONFIG_CONFARGS variable, many places in the mainstream YP documentation that referenced how to pass configure arguments using EXTRA_OECONF needed to also make mention of this new variable. I added many cross-references to the new variable. (From yocto-docs rev: 00f02d45319bab90b72eab89fcb69cbe8bd05bb5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 9b0015d2ee..74deac5452 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -2297,6 +2297,8 @@ However, you might still want to make some adjustments. For example, you can set EXTRA_OECONF + or + PACKAGECONFIG_CONFARGS to pass any needed configure options that are specific to the recipe. CMake: @@ -3011,8 +3013,10 @@ You do not need to add a do_compile step since by default BitBake starts the make command to compile the application. If you need additional make options, you should store them in the - EXTRA_OEMAKE - variable. + EXTRA_OEMAKE + or + PACKAGECONFIG_CONFARGS + variables. BitBake passes these options into the GNU make invocation. Note that a do_install task is still required. Otherwise, BitBake runs an empty do_install task by default. -- cgit v1.2.3-54-g00ecf