From 1a8718c7cd4fbce130c68e3b0f73a64d9fcb9fd3 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 28 May 2014 11:28:05 +0300 Subject: ref-manual: Edits to a few variables in the glossary. I updated the following variables with minor changes: TARGET_CC_ARCH BUILD_CPPFLAGS BUILDSDK_CPPFLAGS CPPFLAGS TARGET_CPPFLAGS (From yocto-docs rev: f7d48ed379778a8568c7e5f812cdb1cbc5339f39) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index cd235e633e..bd1441196b 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -894,8 +894,8 @@ BUILD_CPPFLAGS - Specifies the flags to pass to the C pre-processor and - eventually to both the C and C++ compilers when building + Specifies the flags to pass to the C pre-processor + (i.e. to both the C and the C++ compilers) when building for the build host. When building in the native context, CPPFLAGS @@ -7774,9 +7774,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" It is a common workaround to append LDFLAGS - to TUNE_CC_ARCH in recipes - that build software for the target that would not - otherwise respect the exported + to TARGET_CC_ARCH + in recipes that build software for the target that + would not otherwise respect the exported LDFLAGS variable. -- cgit v1.2.3-54-g00ecf