Difference between revisions of "devkitPro pacman"

From devkitPro
Jump to: navigation, search
(Customising Existing Pacman Install)
(Customising Existing Pacman Install)
Line 25: Line 25:
 
     DEVKITARM=/opt/devkitpro/devkitARM
 
     DEVKITARM=/opt/devkitpro/devkitARM
 
     DEVKITPPC=/opt/devkitpro/devkitPPC
 
     DEVKITPPC=/opt/devkitpro/devkitPPC
 
First initialise the keyring
 
    sudo pacman-key --init
 
  
 
Then import the key which is used to validate the packages. There seem to be issues with keyservers so we specify one here but you may need to look for a working one.
 
Then import the key which is used to validate the packages. There seem to be issues with keyservers so we specify one here but you may need to look for a working one.

Revision as of 16:07, 13 June 2021

Installing devkitPro Pacman

devkitPro provided tools and libraries are managed by the rather wonderful Arch Linux pacman. We provide our own binaries as .pkg for OSX and .deb for debian based linux distributions. On Fedora you can obtain pacman using the command sudo dnf install pacman and edit the pacman configuration files as you would for Arch based linux distros , and pre-existing msys2 installs. We also provide an installer for 64bit windows which sets up a customised msys2 install already set up with the devkitPro packages.Unfortunately msys2 are no longer supporting 32bit and we advise moving to 64 bit if at all possible. You can still obtain the 32bit msys2 installer and follow the manual instructions below.

For Gentoo emerge sys-apps/pacman then edit /etc/pacman.conf and set RootDir = /. Run pacman-key --init then follow the instructions below.

The .deb package can also be used on WSL but you may need to make a symlink for /etc/mtab. See https://github.com/Microsoft/WSL/issues/150

   sudo ln -s /proc/self/mounts /etc/mtab

On Debian based systems install the .deb with (first sudo apt-get install gdebi-core if necessary)

   sudo gdebi devkitpro-pacman.deb

On macOS run the .pkg installer from Terminal with

   sudo installer -pkg devkitpro-pacman-installer.pkg -target /

Then install the Xcode command line tools if you haven't already

   xcode-select --install

And finally reboot your mac to have ennviromnent variables set.

Customising Existing Pacman Install

Note: These instructions are for systems which come with pacman already installed i.e. Arch or Msys2. Do Not follow these instructions if you have dkp-pacman or used the devkitPro installer

For users already using a distro which provides pacman please follow these instructions. This also applies to Fedora and Gentoo below as well as users who wish to use an existing msys2 install. If you're using a pre-existing msys2 install run the commands without sudo. Please also set environment variables as follows :-

   DEVKITPRO=/opt/devkitpro
   DEVKITARM=/opt/devkitpro/devkitARM
   DEVKITPPC=/opt/devkitpro/devkitPPC

Then import the key which is used to validate the packages. There seem to be issues with keyservers so we specify one here but you may need to look for a working one.

  sudo pacman-key --recv BC26F752D25B92CE272E0F44F7FD5492264BB9D0 --keyserver keyserver.ubuntu.com
  sudo pacman-key --lsign BC26F752D25B92CE272E0F44F7FD5492264BB9D0

Now download the devkitpro keyring.

   wget https://pkg.devkitpro.org/devkitpro-keyring.pkg.tar.xz

Then install the keyring. Msys2 users should ignore the sudo part - i.e. type the command line without sudo.

   sudo pacman -U devkitpro-keyring.pkg.tar.xz

Add the devkitPro repositories. Please note that you will require two - one for the libraries and another for the host specific tools.

edit /etc/pacman.conf & add these lines

[dkp-libs]
Server = https://pkg.devkitpro.org/packages

for linux systems also add

[dkp-linux]
Server = https://pkg.devkitpro.org/packages/linux/$arch/

for existing msys2 systems use this one instead of dkp-linux above.

[dkp-windows]
Server = https://pkg.devkitpro.org/packages/windows/$arch/

Now resync the database and update installed packages.

    sudo pacman -Syu

Using Pacman

The customised pacman we ship for OSX and debian based distros is entirely self-contained within /opt/devkitpro/pacman. To avoid polluting the system and avoid clashes with system tools or games which may share the same name as pacman binaries we install helper scripts in /usr/local/bin which temporarily set path and forward to the custom binaries. This means you substitute dkp-pacman for pacman on those systems. Do not add /opt/devkitpro/pacman/bin to your system path, this will cause issues.

Updating Databases

To resync the databases before obtaining updates, this command is similar to apt-get update

   sudo (dkp-)pacman -Sy

To update installed packages, this command is similar to apt-get upgrade

   sudo (dkp-)pacman -Syu

Installing packages

You can list all available packages with

   (dkp)-pacman -Sl

To show only the libraries supplied by devkitPro append dkp-libs

   (dkp-)pacman -Sl dkp-libs

You can search for packages using

   (dkp-)pacman -Ss <search string>

Predefined Groups

We provide several convenient groups which may be installed using sudo (dkp-)pacman -S <group name>

- gp32-dev
- gp2x-dev
- gba-dev 
- nds-dev
- 3ds-dev
- gamecube-dev
- wii-dev
- wiiu-dev
- switch-dev

To list packages use `dkp-pacman -Sl` To install a package use `sudo dkp-pacman -S <name of package>` `sudo dkp-pacman -R <name of package>` will remove an already installed package.