全部

1·The problem with using GCC was that for every target OS or architecture we would need a separate cross compiler.

用gcc存在一个问题，对每一个目标OS或是系统架构，我们都需要一个单独的交叉编译器。

2·This is especially pernicious for cross-compiling, since you probably can't run an executable actually created with the cross compiler.

这对交叉编译尤其不利，因为您可能不能运行实际上是由交叉编译器创建的可执行程序。

3·Do a good job of cross compiler tool chain , the script with the patch set for the compiler to set up their own environment do not want to use.

做好的交叉编译工具链，脚本与补丁集合，适合不想自己架设编译环境的使用。

4·The platform has its own compiler and runtime in order to avoid intermediary libraries that might slow it down and to generate cross platform binaries that can run on multiple systems.

该平台拥有自己的编译器与运行时，目的在于消除可能会降低运行速度的中间库，并且可以生成能够运行在多种系统上的跨平台二进制文件。

5·You may use either a native compiler running under the emulator or a cross-compiler on your host.

既可用模拟器下的原有编译器，也可用主机上的跨编译器。

6·You could even set up a cross-compiler and related tools and poke around in a little more detail.

您甚至可以设置一个交叉编译器以及相关的工具，后面我们会更详细地进行介绍。

7·We needed a portable cross-platform, architecture compiler system that would allow us to develop code on one OS or architecture and deploy it on another with out recompiling.

我们需要一个可移植的、跨平台、跨系统架构的编译器系统，这样我们可以在一个OS或者系统架构上开发代码，在另一个上面进行部署而无需重新编译。

8·Setting up a cross-compiler toolchain from scratch is not an easy task: it involves downloading the sources, patching, configuring, compiling, setting up headers, installation, and much, much more.

重头设置交叉编译器工具链可不是一项简单的任务：它包括下载源代码、修补补丁、配置、编译、设置头文件、安装以及很多很多的操作。

9·You may also need to configure a cross-compiler to generate the binaries you intend to test.

也许还需要配置跨编译器以生成想要测试的二进制文件。

10·The compiler most people use is GCC, which can be a little daunting to set up (particularly as a cross-compiler) if you have never done this before.

大部分人使用的编译器是gcc，如果您以前从来没有这样设置过，设置起来可能令人望而生畏(尤其是将其设置为一个交叉编译器)。