Lines Matching full:your

9 for cross-compiling your code to a different architecture. It assumes you
13 However, this document is *not* a "how to" and won't help you setting your
31 when compiling your code.
44 you're compiling to, where your tools are, etc.
49 to build your software, that is specific to your target. It's not enough to
50 have your host's libraries installed.
55 all your binaries and libraries are in the same directory, which may not
56 true when your cross-compiler was installed by the distribution's package
63  * be in a single directory, or spread out across your system
65  * need special options, which your build system won't be able to figure
101 define the specific behaviour of your code (PCS, extensions),
107 Once your target is specified, it's time to pick the hardware you'll
119 code for your specific hardware, which may mean orders of magnitude
122 For example, if your target is ``arm-none-eabi``, the default CPU will
124 whereas if your triple is ``armv7a-none-eabi``, it'll be Cortex-A8 with
131 There are three main options to control access to your cross-compiler:
134 and headers that are specific to your target.
138 #. When you have extracted your cross-compiler from a zip file into
140    root directory where you have unpacked your file, and Clang will
143    In this case, your setup should be pretty much done (if no
149    sure the target triple you set is *also* the prefix of your
164 All libraries that you compile as part of your build will be
165 cross-compiled to your target, and your build system will probably
171 your code, it will get every dependency wrong, and your compilation
174 Also, finding the libraries for your target are not as easy
175 as for your host machine. There aren't many cross-libraries available
177 from source, or download the package for your target platform,
184 of your build can get things wrong when setting their own library
193 copies of your libraries and (possibly) headers.