Getting Started: Difference between revisions

From devkitPro
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
For Windows users getting started with devkitPro toolchains is made easy by the convenient [http://sourceforge.net/projects/devkitpro/files/Automated%20Installer/ Windows Installer/Updater] package. It is strongly recommended that windows users stick with this rather than attempting to set up the packages manually. The updater handles all the sticky little details of installation required for properly functioning toolchains. This is a web based installer so please ensure that you have a net connection, your Internet Explorer proxy settings are correct and that any firewall software you have installed allows the application to access the net.
Getting started with devkitPro toolchains is made rather easy with convenient pacman packages.


For those of you who wish to install offline a "Download only" option is provided to download the packages without installing for later installation on another machine. This is best used by running the installer from a removable drive where it will store the downloaded packages. The "Download and install/install from downloaded files" option will pick up the packages from the directory the installer is running from.  
= Setup =
Install [http://devkitpro.org/ devkitA64]. If it's already installed, update it using sudo (dkp-)pacman -Syu. On Windows, there's a [https://github.com/devkitPro/installer/releases/latest graphical installer]. On Unix-like platforms such as Linux/macOS, there's [https://github.com/devkitPro/pacman/releases/latest pacman].


For other platforms there are a few options available. Recently we've added some experimental perl scripts which parse the ini file used for the windows updater - these can be found in the  [https://sourceforge.net/projects/devkitpro/files/Automated%20Installer/ Automated Installer files]. These will work on both OSX and linux, selecting the correct 32/64 bit binaries on linux.
==Windows==


While the scripts should be the preferred method, you can also install the binaries manually or use the buildscripts to build and install the latest release versions.
* If you already use msys2 then you can follow the instructions at https://github.com/devkitPro/pacman/releases/latest to add the devkitPro repositories.


Where possible you should stick to the binary distributions - building from source can be a path of frustration even for seasoned developers. The following pages cover installing each toolchain in detail.
Otherwise


[[Getting_Started/devkitARM | Manual instructions for installing devkitARM]]
* [https://github.com/devkitPro/installer/releases download the latest version of the graphical installer] from github and run it, following the instructions as you go.
* An Internet connection is required.
* Once the installer has finished, launch MSYS from:
** Windows 7 and earlier: Start -> All Programs -> devkitPro -> MSYS
** Windows 8 and 8.1: Right click on the Start screen and select 'All Apps'. You should find MSYS there.
** Windows 10 (pre-Anniversary Update): Start -> All Apps -> devkitPro -> MSYS
** Windows 10 (post-Anniversary Update): Start -> devkitPro -> MSYS


[[Getting_Started/devkitPPC | Manual instructions for installing devkitPPC]]
==Unix-like platforms==
Currently devkitPro provides precompiled versions of devkitA64 for the following Unix-like platforms: Linux (x86_64), macOS (x86_64). Note that Linux x86_64 binaries are usable under WSL.


[[Getting_Started/devkitPSP | Manual instructions for installing devkitPSP]]
* Follow the instructions to install pacman found at https://github.com/devkitPro/pacman/releases/latest
* run sudo (dkp-)pacman -S switch-dev to install the tools and libraries for switch development
* logout and login again to get the environment settings needed.


Where a binary is not provided then you should use the most recent stable release of the [http://sourceforge.net/projects/devkitpro/files/buildscripts/ buildscripts]. The buildscripts in the git repositories should be avoided since the buildscripts found there will often contain the next iteration of a given toolchain rather than the current stable release and may only be usable by our developers. Using these scripts is a simple matter of extracting the archive, running ./build-devkit.sh from a bash shell and following the prompts. The scripts will also build and install the current support libraries from the release tarballs. The readme supplied with the buildscripts details some dependencies which need to be in place before starting a build.
==BuildScripts==
Where possible you should stick to the binary distributions - building from source can be a path of frustration even for seasoned developers. Where a binary is not provided then you should use the most recent stable release of the https://github.com/devkitPro/buildscripts/releases/latest buildscripts]. The buildscripts in the git repositories should be avoided since the buildscripts found there will often contain the next iteration of a given toolchain rather than the current stable release and may only be usable by our developers. Using these scripts is a simple matter of extracting the archive, running ./build-devkit.sh from a bash shell and following the prompts. The scripts will also build and install the current support libraries from the release tarballs. The readme supplied with the buildscripts details some dependencies which need to be in place before starting a build.

Revision as of 02:16, 6 June 2018

Getting started with devkitPro toolchains is made rather easy with convenient pacman packages.

Setup

Install devkitA64. If it's already installed, update it using sudo (dkp-)pacman -Syu. On Windows, there's a graphical installer. On Unix-like platforms such as Linux/macOS, there's pacman.

Windows

Otherwise

  • download the latest version of the graphical installer from github and run it, following the instructions as you go.
  • An Internet connection is required.
  • Once the installer has finished, launch MSYS from:
    • Windows 7 and earlier: Start -> All Programs -> devkitPro -> MSYS
    • Windows 8 and 8.1: Right click on the Start screen and select 'All Apps'. You should find MSYS there.
    • Windows 10 (pre-Anniversary Update): Start -> All Apps -> devkitPro -> MSYS
    • Windows 10 (post-Anniversary Update): Start -> devkitPro -> MSYS

Unix-like platforms

Currently devkitPro provides precompiled versions of devkitA64 for the following Unix-like platforms: Linux (x86_64), macOS (x86_64). Note that Linux x86_64 binaries are usable under WSL.

  • Follow the instructions to install pacman found at https://github.com/devkitPro/pacman/releases/latest
  • run sudo (dkp-)pacman -S switch-dev to install the tools and libraries for switch development
  • logout and login again to get the environment settings needed.

BuildScripts

Where possible you should stick to the binary distributions - building from source can be a path of frustration even for seasoned developers. Where a binary is not provided then you should use the most recent stable release of the https://github.com/devkitPro/buildscripts/releases/latest buildscripts]. The buildscripts in the git repositories should be avoided since the buildscripts found there will often contain the next iteration of a given toolchain rather than the current stable release and may only be usable by our developers. Using these scripts is a simple matter of extracting the archive, running ./build-devkit.sh from a bash shell and following the prompts. The scripts will also build and install the current support libraries from the release tarballs. The readme supplied with the buildscripts details some dependencies which need to be in place before starting a build.

Retrieved from "https://devkitpro.org/wiki/w/index.php?title=Getting_Started&oldid=359"