Lines Matching full:environment

77 2. *Source the Cross-Toolchain Environment Setup File:* As described
79 cross-toolchain environment setup script in the directory that the
82 the string "environment-setup" and contains the machine architecture,
88 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
110 environment variable provides the minimal arguments for GNU
118 is derived from the name of the environment setup script found in the
122 script is ``environment-setup-armv5te-poky-linux-gnueabi``. Thus, the
136 To learn about environment variables established when you run the
137 cross-toolchain environment setup script and how they are used or
161 environment variables established when you run the cross-toolchain
162 environment setup script. The environment variables are subject to
166 example that lets you see how you can use cross-toolchain environment
176 Environment Variables Set in the SDK Setup Script:* Because matching
178 retain their values based on the environment setup script.
181 Environment Variables from the SDK Setup Script:* Specifically
183 results in the environment settings of the variables being
188 Equivalent Environment Variables from the SDK Setup Script:*
190 environment variables being overwritten. In this case, the
204 In a new shell environment variables are not established for the SDK
220 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
267 2. *Source the Cross-Toolchain Environment Setup File:* As described
269 cross-toolchain environment setup script in the directory that the
272 the string "environment-setup" and contains the machine architecture,
278 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
282 identical to the value that is set when you run the SDK environment
300 value used for :term:`CC` is the value set when the SDK environment setup
312 You can override the :term:`CC` environment variable with the same
357 environment variable.
381 use the SDK environment variables regardless of the values in the