Toolchain

Binary releases for tools such as 3dsxtool, smdhtool, and the GNU Compiler Toolchain are made available for the following platforms:

• Windows (XP or later)
• Mac OS X (10.6 or later)
• Linux (i386 and AMD64)

Please remember that binary releases for your platform may have been compiled using a cross-compiler (ex. i686-unknown-mingw32-gcc on a Mac OS X host). This may cause problems, and may result in a binary toolchain release that is broken and unusable on your machine. Please be patient and we will try to fix these problems when they occur.

The OpenCTR toolchain is made available in the following formats:

• XZ-Compressed tarball archive (.tar.xz)
• ZIP archive (.zip)
• Windows NSIS Installer (.msi)
• Mac OS X Package (.pkg)
• Debian GNU/Linux Package (.deb)
• Red Hat/Fedora Package (.rpm)

The various installer packages (.msi, .pkg, .rpm) may not be available for every release, but the tar.xz and zip archives will always be made available for every release.

Debian and Red Hat packages are automatically generated and uploaded, but are not a part of any repository at this time.

Libraries

Unlike the toolchain, a binary release of an OpenCTR library is never platform specific. Libraries (such as libctr) are cross-compiled to ARM, meaning it makes no difference if the library was created on e.g. Windows and then used on e.g. Linux.

A typical library release package contains one or header files, and one or more static library files. Often, these files will be inside subdirectories, and it can be important that they be installed with the same name and location.

Libraries are usually released as both tar.xz and zip archives. UNIX-Like users (including Mac OS X) should download tar.xz files, while Windows users should download the zip archive. After downloading the release, extract it into the installation folder, usually the root of OpenCTR.

Binary releases of the OpenCTR toolchain usually have libraries like libctr bundled, but the user will still need to install any future updates themselves.