== Configuring environment ==
At this time, a linux-esque environment (<i>not</i> msys2) is required - though work into Windows support is ongoing. For now, Windows users can use [https://docs.microsoft.com/en-us/windows/wsl/install-win10 WSL] or a [https://itsfoss.com/install-linux-in-virtualbox/ virtual machine]. Your first step is to install [https://devkitpro.org/wiki/devkitPro_pacman devkitPro pacman], downloading the Linux or OSX versions as appropriate for your setup. Once installed, you can use one of <syntaxhighlight inline>dkp-pacman -S <package></syntaxhighlight> or <syntaxhighlight inline>pacman -S <package></syntaxhighlight> to install packages! Start off by installing <syntaxhighlight inline>devkitPPC</syntaxhighlight>, followed by <syntaxhighlight inline>devkit-env</syntaxhighlight> on Linux or Windows. If that worked without error, your next step is to [https://gitlab.com/QuarkTheAwesome/wiiu-fling/blob/master/README.md install wiiu-fling] using the instructions in that link. That will add some extra Wii U-related packages to pacman, including most things you'll need to develop homebrew!
== Making Native Apps (wut) ==
The best solution for making Wii U homebrew at this time is [https://github.com/decaf-emu/wut wut]; an actively-developed toolchain that can build native RPX apps. RPX apps have a high filesize limit, can be launched through HBL or installed to the System Menu as a channel, and can take advantage of many Nintendo features previously unavailable to homebrew. It's recommended to use wut for all new projects.
If you followed the wiiu-fling install instructions above, you should be able to install the <syntaxhighlight inline>wut-linux</syntaxhighlight> or <syntaxhighlight inline>wut-
osx</syntaxhighlight> packages, depending on your system.
There's plenty of examples of using wut, such as [https://github.com/decaf-emu/wut/tree/master/samples its own examples]; along with real-world apps. See [[#Guides]] for more info on getting started with wut.