| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| ns32ktoolchain [2019/01/24 00:23] – [Binary format support] admin | ns32ktoolchain [2020/02/14 13:30] – [Overview] admin |
|---|
| The **[[wp>GNU_toolchain|GNU Toolchain]]** is a collection of opensource software used for developing other software and OS-es. GNU Toolchain "by design" supports high portability and cross-compilation. It includes (among other tools) the **[[wp>GNU_Binutils|GNU Binutils]]** (assembler, linker e.t.c) and **GCC** (**[[wp>GNU Compiler Collection]]**: c, c++, fortran, ada e.t.c.). | The **[[wp>GNU_toolchain|GNU Toolchain]]** is a collection of opensource software used for developing other software and OS-es. GNU Toolchain "by design" supports high portability and cross-compilation. It includes (among other tools) the **[[wp>GNU_Binutils|GNU Binutils]]** (assembler, linker e.t.c) and **GCC** (**[[wp>GNU Compiler Collection]]**: c, c++, fortran, ada e.t.c.). |
| |
| To run GNU Toolchain you have to use [[wp>Unix-like]] environment on real *NIX (Free/Net/Open-BSD Linux e.t.c.) with GNU tools pre-installed or UNIX-like environment like **[[wp>Cygwin]]** or **[[wp>MinGW]]+MSYS** for Windows. Virtual machine to run *NIX would be good too. | To run GNU Toolchain you have to use [[wp>Unix-like]] environment on real *NIX (Free/Net/Open-BSD Linux e.t.c.) with GNU tools pre-installed or UNIX-like environment like **[[wp>Cygwin]]** or **[[https://www.msys2.org/|MSYS2]]** for Windows. Virtual machine to run *NIX would be good too. |
| |
| To support cross-compilation there are three system names that the building scripts knows about: the machine you are building on (''BUILD''), the machine that you are building for (''HOST''), and the machine that toolchain will produce code for (''TARGET''). When you configure toolchains, you specify these with ''--build='', ''--host='', and ''--target=''. | To support cross-compilation there are three system names that the building scripts knows about: the machine you are building on (''BUILD''), the machine that you are building for (''HOST''), and the machine that toolchain will produce code for (''TARGET''). When you configure toolchains, you specify these with ''--build='', ''--host='', and ''--target=''. |
| - [[http://wiki.sensi.org/download/doc/shared.txt|shared.txt]] Solaris shared library FAQ\\ | - [[http://wiki.sensi.org/download/doc/shared.txt|shared.txt]] Solaris shared library FAQ\\ |
| - [[http://wiki.sensi.org/download/doc/dso.txt|dso.txt]] DSO explanation from SGI IRIX\\ | - [[http://wiki.sensi.org/download/doc/dso.txt|dso.txt]] DSO explanation from SGI IRIX\\ |
| - [[http://wiki.sensi.org/download/doc/mipsabi32.pdf|mipsabi32.pdf]] MIPS ABI\\ | - "Linkers and Loaders" by John R. Levine\\ |
| - "Linkers and Loaders" by John R. Levine | - [[https://wiki.osdev.org/System_V_ABI|System V ABI]]\\ |
| | -- [[http://wiki.sensi.org/download/doc/mipsabi32.pdf|mipsabi32.pdf]] MIPS ABI |
| |
| ==== Building binutils ==== | ==== Building binutils ==== |
