We proudly present devkitPro pacman :)
Posted: Fri Mar 23, 2018 3:26 am
We've spent considerable time putting together linux and osx binaries of pacman, the popular package manager for Arch Linux. This now allows us to produce prebuilt packages of libraries useful for porting which were formerly provided by a somewhat awkward and unreliable Makefile. The windows installer has now been upgraded to provide an msys2 install which provides pacman for windows users too.
Once installed you will find an msys2 shortcut in your start menu under devkitPro. This will launch a shell from where you can access pacman. Use `pacman -Sl` to list all the packages you can install or `pacman -Sl dkp-libs` for just devkitPro supplied packages. Installing is a simple `pacman -S <name of package` and this will also install any needed dependencies.
More details and instructions for OSX & various linux distros can be found on the wiki
Please note that this now means that the devkitPro toolchain infrastructure can only be installed to /opt/devkitpro (this is achieved on windows with msys fstab) and no support will be provided for any other install location. We have to do this because many of the libraries and supporting tools end up with absolute paths baked in at compile time and fixing everything to allow abitrary install locations is likely to be a never ending, if not impossible task. It does mean that users will no longer be faced with issues that have arisen in the past from attempting to compile portlibs with no prior knowledge or using some random portlibs binaries that have been compiled in the wrong order.
Once installed you will find an msys2 shortcut in your start menu under devkitPro. This will launch a shell from where you can access pacman. Use `pacman -Sl` to list all the packages you can install or `pacman -Sl dkp-libs` for just devkitPro supplied packages. Installing is a simple `pacman -S <name of package` and this will also install any needed dependencies.
More details and instructions for OSX & various linux distros can be found on the wiki
Please note that this now means that the devkitPro toolchain infrastructure can only be installed to /opt/devkitpro (this is achieved on windows with msys fstab) and no support will be provided for any other install location. We have to do this because many of the libraries and supporting tools end up with absolute paths baked in at compile time and fixing everything to allow abitrary install locations is likely to be a never ending, if not impossible task. It does mean that users will no longer be faced with issues that have arisen in the past from attempting to compile portlibs with no prior knowledge or using some random portlibs binaries that have been compiled in the wrong order.