For that value, you simply write down the folder that your clone of the WUT repo is stored in. The WUT folder contains the tools, include and lib folders. In my case, I cloned the wut repo into the same folder where my devkitPPC folder was (in ~/wiiu/devkitpro), so I simply needed to write "$DEVKITPRO/wut" since I already had devkitPro set up.How do you put WUT_ROOT in your environment I know where it goes but what exactly are you supposed to write down?
So if the master folder is in C:/devkitPRO you would write C:/DevkitPro/wut in your environment or does it have to be exactly $DEVKITPRO/wut? Do you have to put the whole wut-master folder in C:/DevkitProas well or just the lib & include fodersFor that value, you simply write down the folder that your clone of the WUT repo is stored in. The WUT folder contains the tools, include and lib folders. In my case, I cloned the wut repo into the same folder where my devkitPPC folder was (in ~/wiiu/devkitpro), so I simply needed to write "$DEVKITPRO/wut" since I already had devkitPro set up.
You said that you put the "wut" folder inside "C:\devkitPro\devkitPPC." In that case, your variable needs to be "C:\devkitPro\devkitPPC\wut." Notice how the variable is a direct path to the folder we want. Using $DEVKITPRO or $DEVKITPPC won't work unless they have already been defined as other values.Thank you but its still not working for me>
I have put the "wut" folder from here> https://github.com/decaf-emu/wut in c:/devkitPro/devkitPPC I have put in my environment variables> $DEVKITPRO/wut I have put> homebrew_launcher-homebrew_launcher_rpx master folder in c:/homebrew_launcher-homebrew_launcher_rpx. Start cmd type in "make" and I'm still getting this same error?>,
Thank you its worked, it was calling it "WUT_ROOT" that did the trick, that was my mistake.You said that you put the "wut" folder inside "C:\devkitPro\devkitPPC." In that case, your variable needs to be "C:\devkitPro\devkitPPC\wut." Notice how the variable is a direct path to the folder we want. Using $DEVKITPRO or $DEVKITPPC won't work unless they have already been defined as other values.
Also, are you putting this at the end of the PATH variable? If so, that's also a problem. It also needs to be put into its own variable (the error above tells you this, "C:\devkitPro\devkitPPC\wut" needs to be added to its own variable called "WUT_ROOT", rather than being put into the PATH variable.)
Thank you its worked, it was calling it "WUT_ROOT" that did the trick, that was my mistake.
I spoke to soon. Its working but at the end I am getting this error below. Now its something to do with the libmad.a file in devkitPro\libogc\wii\/libmad.a file does the wii folder need updating for this to work I'm not sure where to get the updated files from? also it seems to be compiling a .elf version of the homebrew launcher I was after an .rpx version?
@CreeperMarioDo you have the portlibs and libogc attached to this release? Your files have a different size.
https://github.com/dimok789/homebrew_launcher/releases/tag/v1.3
@CreeperMario
I have corrected those above issues now. I am now on to my next issue actually compiling the .rpx file at the end I cant compile the make-tools.bat file to actually make the tools required for "elf2rpl". When I click on the "make-tools.bat" file it just disappears asap, instead of compiling the tools needed in the "bin" file. I must need something for my pc to be able the make-tools.bat file to create the right tools in the bin folder? I keep getting> Makefile:8: "msbuild not found, try building with make-tools.bat from vcvars prompt" and it wont build the bin file with the correct tools to compile the .rpx file the rest is working thanks to you.
Thanks that works a treat. I've actually compiled it now after some fantastic help and some effort.Extract the attached binaries to wut\bin. I have compiled them.
msbuild is part of Visual Basic https://www.visualstudio.com/de/vs/community/
If you connect a Wii Remote to your console, you can point at the TV screen and select a homebrew. But no button-only navigation, yet.is there any way to use buttons to navigate instead of using touchscreen?
WOW... I guess I can't use Homebrew because my GamePad touchscreen is brokenIf you connect a Wii Remote to your console, you can point at the TV screen and select a homebrew. But no button-only navigation, yet.
Well you should install haxchi yes and then coldboothax (which requires haxchi and overwrites) to autoboot wiiu menu with signature patches and region patches and install homebrew launcher channel RPX to wiiu menu (from here) using wup installer and directly launch it from there just like a normal app. But you need to follow all the steps carefully with no usb connected during haxchi and coldboothax (cbhc) instalations. + the DS title should be on nand memory (internal memory of wiiu) if you delete it or move it to usb after cbhc installation ur wiiu won't boot anymore (you have to uninstall cbhc 1st if you want to delete it or move it) but remember to do all these installations before homebrew RPX you need to load the regular homebrew launcher of course from loadiine.ovh site on ur wiiu browser (download the correct files in the correct directory on ur fat32 formated sd to dont get error) in loadiine.ovh if homebrew launcher 1.4 option is always freezing ur wiiu try homebrew launcher 1.3 option it works for me the best as well almost 100% with no crashesI bought a new wii u last month....I have not soft modded/hacked anything yet.
My question is, what is the best/preferred way to install homebrew launcher?
Doing a google search I got a hit on another site titled "Wii U Permanent Homebrew Channel / Launcher Exploit Tutorial [Haxchi 2.0 Wii U Hack]" and which involves purchasing a DS game and modifying the DS game files to run Homebrew launcher straight from system NAND.
Since I have not soft modded my wii u, I am looking to perform the least amount of mods to my console, my goal is to eventually install disk based games to system nand by using the Brazilian method, of course I will have the games on USB drive.
Anyone my question is, what is best method to install Homebrew Launcher? After I get my games ripped to the hard drive, I doubt I will even need to keep Homebrew Launcher, so I could just delete the Homebrew Launcher at some future date too.
Thanks for your input/advise on this,
KL