diff options
author | Dylan Baker <dylan@pnwbakers.com> | 2020-04-20 09:55:51 -0700 |
---|---|---|
committer | Jussi Pakkanen <jpakkane@gmail.com> | 2020-04-21 00:05:12 +0300 |
commit | 182f40d25add336531b4127e410af8bcbe067575 (patch) | |
tree | e431c5edeeb0e0645bbe902e86da36ee743ba474 | |
parent | 278c294aa45efc3e8b068bcd7632828ed5c92523 (diff) | |
download | meson-182f40d25add336531b4127e410af8bcbe067575.zip meson-182f40d25add336531b4127e410af8bcbe067575.tar.gz meson-182f40d25add336531b4127e410af8bcbe067575.tar.bz2 |
docs/cross-compilation: Note appropriate values for cpu_family [skip ci]
Also note that meson doesn't use `el` on the end of the cpu_family to
mark endianness, that the endian field needs to be set appropriately.
-rw-r--r-- | docs/markdown/Cross-compilation.md | 20 |
1 files changed, 12 insertions, 8 deletions
diff --git a/docs/markdown/Cross-compilation.md b/docs/markdown/Cross-compilation.md index 9e64a3e..4c4b7bf 100644 --- a/docs/markdown/Cross-compilation.md +++ b/docs/markdown/Cross-compilation.md @@ -195,14 +195,18 @@ surprisingly, `build_machine`, `host_machine` and `target_machine`. Determining the operating system of your host machine is simply a matter of calling `host_machine.system()`. -There are two different values for the CPU. The first one is -`cpu_family`. It is a general type of the CPU. Common values might -include `x86`, `arm` or `x86_64`. The second value is `cpu` which is a -more specific subtype for the CPU. Typical values for a `x86` CPU -family might include `i386` or `i586` and for `arm` family `armv5` or -`armv7hl`. Note that CPU type strings are very system dependent. You -might get a different value if you check its value on the same machine -but with different operating systems. +There are two different values for the CPU. The first one is `cpu_family`. It +is a general type of the CPU. This should have a value from [the CPU Family +table](Reference-tables.md#cpu-families). *Note* that meson does not add +`el` to end cpu_family value for little endian systems. Big endian and little +endian mips are both just `mips`, with the `endian` field set approriately. + +The second value is `cpu` which is +a more specific subtype for the CPU. Typical values for a `x86` CPU family +might include `i386` or `i586` and for `arm` family `armv5` or `armv7hl`. +Note that CPU type strings are very system dependent. You might get a +different value if you check its value on the same machine but with different +operating systems. If you do not define your host machine, it is assumed to be the build machine. Similarly if you do not specify target machine, it is assumed |