From 61a8bb03ac1446e4cc3e38900d1e066c50ce3435 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 18 May 2018 15:15:34 -0700 Subject: sdk-manual: Updates to "Running the Extensible SDK Environment Setup Script" Some Minor edits to this section. Also, a scrub of the list of variables exported when running the install script. The list is out of date and is missing many variables. I noted these in comments for now and will add them in later. (From yocto-docs rev: 739a2ca42ee798625492ddb51a32ad09f80aa960) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/sdk-manual/sdk-extensible.xml | 48 +++++++++++++++++------------ 1 file changed, 29 insertions(+), 19 deletions(-) (limited to 'documentation/sdk-manual/sdk-extensible.xml') diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml index 0389cb4448..de0e7a7379 100644 --- a/documentation/sdk-manual/sdk-extensible.xml +++ b/documentation/sdk-manual/sdk-extensible.xml @@ -181,7 +181,7 @@ Once you have the SDK installed, you must run the SDK environment - setup script before you can actually use it. + setup script before you can actually use the SDK. This setup script resides in the directory you chose when you installed the SDK, which is either the default poky_sdk directory or the directory you @@ -205,31 +205,41 @@ SDK environment now set up; additionally you may now run devtool to perform development tasks. Run devtool --help for further details. - When you run the setup script, many environment variables are - defined: + Running the setup script defines many environment variables: - SDKTARGETSYSROOT - The path to the sysroot used for cross-compilation - PKG_CONFIG_PATH - The path to the target pkg-config files - CONFIG_SITE - A GNU autoconf site file preconfigured for the target + AR - The minimal command and arguments to run 'ar' + + AS - The minimal command and arguments to run the assembler CC - The minimal command and arguments to run the C compiler - CXX - The minimal command and arguments to run the C++ compiler + CFLAGS - Suggested C flags + CONFIG_SITE - A GNU autoconf site file preconfigured for the target + CONFIGURE_FLAGS - The minimal arguments for GNU configure CPP - The minimal command and arguments to run the C preprocessor - AS - The minimal command and arguments to run the assembler - LD - The minimal command and arguments to run the linker + CPPFLAGS - Suggested preprocessor flagsexport CROSS_COMPILE + CXX - The minimal command and arguments to run the C++ compiler + CXXFLAGS - Suggested C++ flags + DEPLOY_DIR_IMAGE GDB - The minimal command and arguments to run the GNU Debugger - STRIP - The minimal command and arguments to run 'strip', which strips symbols - RANLIB - The minimal command and arguments to run 'ranlib' + + LD - The minimal command and arguments to run the linker + LDFLAGS - Suggested linker flags when you use CC to link + + NM - The minimal command and arguments to run 'nm' OBJCOPY - The minimal command and arguments to run 'objcopy' OBJDUMP - The minimal command and arguments to run 'objdump' - AR - The minimal command and arguments to run 'ar' - NM - The minimal command and arguments to run 'nm' + + PATH - The Linux variable that specifies the set of directories where executable programs are located. + PKG_CONFIG_PATH - The path to the target pkg-config files + + RANLIB - The minimal command and arguments to run 'ranlib' + SDKTARGETSYSROOT - The path to the sysroot used for cross-compilation + STRIP - The minimal command and arguments to run strip, which is used to strip symbols. TARGET_PREFIX - The toolchain binary prefix for the target tools - CROSS_COMPILE - The toolchain binary prefix for the target tools - CONFIGURE_FLAGS - The minimal arguments for GNU configure - CFLAGS - Suggested C flags - CXXFLAGS - Suggested C++ flags - LDFLAGS - Suggested linker flags when you use CC to link - CPPFLAGS - Suggested preprocessor flags -- cgit v1.2.3-54-g00ecf