Welcome to the Toolchain Project Wiki#

The toolchain project provides the essential programming tools necessary to develop Neutrino applications.

GCC#

Description

The GNU Compiler Collection (GCC) is a widely used multi-language (C, C++, ...) multi-target (ARM, MIPS, PPC, SH4, X86, ...) compiler available on supported hosts.

How to build

1. Check out source from branch.
2. Change directory into a build directory that matches the desired configuration. If you want the compiler to execute on a Linux host, and generate binaries for an SH4 target, change into the llinux-x86-o-ntosh/ directory. If you desire a Windows hosted compiler that generates binaries for a MIPS target, change into win32-x86-o-ntomips/
3. Remove any existing files with the exception of 'GNUmakefile'.
4. Type 'make'. The build will take sometime to complete.
5. Once make has successfully completed, if you are on a system that has write permissions on $QNX_HOST and $QNX_TARGET, switch to superuser/administrator access.
6. Type 'make install'. The build system will install the compiler into the directories specified in root 'build-hooks' file.

Branches

GDB#

Description

The GNU Debugger (GDB) is a standard source-level debugger available on several platforms. GDB can be used as a native debugger on x86 Neutrino hosts and as a host side debugger with remote debugging facilities necessary to debug embedded targets.

How to build

1. Check out source from branch.
2. Change directory into a build directory that matches the desired configuration. If you want thedebugger to execute on a Linux host, and debug Sh4 binaries, change into the llinux-x86-o-ntosh/ directory. If you desire a Windows hosted debugger that debugs MIPS binaries, change into win32-x86-o-ntomips/
3. Remove any existing files with the exception of 'GNUmakefile'.
4. Type 'make'. The build will take sometime to complete.
5. Once make has successfully completed, if you are on a system that has write permissions on $QNX_HOST and $QNX_TARGET, switch to superuser/administrator access.
6. Type 'make install'. The build system will install the debugger into the directories specified in root 'build-hooks' file. (Default: $QNX_HOST/usr/bin)

Branches

binutils#

The GNU binutils are a set of binary utilities that are used to manipulate object files. The primary utilities used in the toolchain are the assembler (gas) and the linker (ld).

How to build

1. Check out source from branch.
2. Change directory into a build directory that matches the desired configuration. If you want the binutils to execute on a Linux host, and generate binaries for an SH4 target, change into the llinux-x86-o-ntosh/ directory. If you desire a Windows hosted binutils that generates binaries for a MIPS target, change into win32-x86-o-ntomips/
3. Remove any existing files with the exception of 'GNUmakefile'.
4. Type 'make'. The build will take sometime to complete.
5. Once make has successfully completed, if you are on a system that has write permissions on $QNX_HOST and $QNX_TARGET, switch to superuser/administrator access.
6. Type 'make install'. The build system will install the binutils into the directories specified in root 'build-hooks' file.

Branches

make#

Make is a utility for controlling and automating the build of applications.

How to build

1. Check out source from branch.
2. Change directory into a build directory that matches the desired configuration. If you want the make executable to run on a Linux host, change into the llinux-x86-o/ directory. If you desire a Windows hosted make executable, change into win32-x86-o/
3. Remove any existing files with the exception of 'GNUmakefile'.
4. Type 'make'. The build will take sometime to complete.
5. Once make has successfully completed, if you are on a system that has write permissions on $QNX_HOST and $QNX_TARGET, switch to superuser/administrator access.
6. Copy the make executable into $QNX_HOST/usr/bin/

Branches

nasm#

NASM, is a free Intel x86 assembler that allows assembly applications to be ported across 32-bit x86 OSes.

How to build

1. Check out source from branch.
2. Change directory into a build directory that matches the desired configuration. If you want the nasm executable to run on a Linux host, change into the llinux-x86-o/ directory. If you desire a Windows hosted nasm executable, change into win32-x86-o/
3. Remove any existing files with the exception of 'GNUmakefile'.
4. Type 'make'. The build will take sometime to complete.
5. Once make has successfully completed, if you are on a system that has write permissions on $QNX_HOST and $QNX_TARGET, switch to superuser/administrator access.
6. Copy the nasm executable into $QNX_HOST/usr/bin/

Branches