Lines 82-88
built by crossdev won't interfere with the host's native toolchain.
Link Here
|
82 |
Certain environment variables used by the Gentoo toolchain and Portage can |
82 |
Certain environment variables used by the Gentoo toolchain and Portage can |
83 |
thoroughly confuse developers inexperienced with cross development. The |
83 |
thoroughly confuse developers inexperienced with cross development. The |
84 |
following table explains some tricky variables and provides sample values based |
84 |
following table explains some tricky variables and provides sample values based |
85 |
on the cross development examples presented in this guide. See the <uri |
85 |
on the cross development examples presented in this guide. See <uri |
86 |
link="#terminology">More Terminology and Variables</uri> for more |
86 |
link="#terminology">More Terminology and Variables</uri> for more |
87 |
unusual variables and related concepts. |
87 |
unusual variables and related concepts. |
88 |
</p> |
88 |
</p> |
Lines 173-187
PDA we wanted to develop for, the above table would look like:
Link Here
|
173 |
machine from the one it was compiled on (CBUILD != CHOST && CHOST != CTARGET) |
173 |
machine from the one it was compiled on (CBUILD != CHOST && CHOST != CTARGET) |
174 |
</dd> |
174 |
</dd> |
175 |
|
175 |
|
176 |
<dt><c>CBUILD: build system</c></dt> |
|
|
177 |
<dd>The system type you compile binaries on</dd> |
178 |
|
179 |
<dt><c>CHOST: host system</c></dt> |
180 |
<dd>The system type you execute binaries on</dd> |
181 |
|
182 |
<dt><c>CTARGET: target system</c></dt> |
183 |
<dd>The system type you compile binaries for</dd> |
184 |
|
185 |
<dt><c>sysroot: system root</c></dt> |
176 |
<dt><c>sysroot: system root</c></dt> |
186 |
<dd>The root directory a compiler uses to find its standard headers and libraries. Sometimes a compiler wants more than just standard headers and libraries in this directory, as though they were "standard" too. We'll explain how to resolve this when it happens in future chapters.</dd> |
177 |
<dd>The root directory a compiler uses to find its standard headers and libraries. Sometimes a compiler wants more than just standard headers and libraries in this directory, as though they were "standard" too. We'll explain how to resolve this when it happens in future chapters.</dd> |
187 |
|
178 |
|
Lines 200-206
PDA we wanted to develop for, the above table would look like:
Link Here
|
200 |
<dt><c>CRT</c></dt> |
191 |
<dt><c>CRT</c></dt> |
201 |
<dd>C RunTime<!-- what does this have to do with crossdev? --></dd> |
192 |
<dd>C RunTime<!-- what does this have to do with crossdev? --></dd> |
202 |
|
193 |
|
203 |
<dt>Tuple</dt> |
194 |
<dt><c>Tuple</c></dt> |
204 |
<dd>For crossdev, this is defined as a string in the <c>ARCH-VENDOR-OS-LIBC</c> format. See <c>crossdev -t help</c> for information on how exactly this string can be completed.</dd> |
195 |
<dd>For crossdev, this is defined as a string in the <c>ARCH-VENDOR-OS-LIBC</c> format. See <c>crossdev -t help</c> for information on how exactly this string can be completed.</dd> |
205 |
|
196 |
|
206 |
</dl> |
197 |
</dl> |
207 |
- |
|
|