Sorry for the double post but yea, that looked golden.So if this is right now it should compile the newest nightly of sm64ex, right?
Sorry for the double post but yea, that looked golden.So if this is right now it should compile the newest nightly of sm64ex, right?
Sorry for the double post but yea, that looked golden.
What you talking about.....By masking the problem away. Please stop this false hints.
Pacman is a package manager, sudo is a command to switch the user. Completely different things and nothing with Win or Lin.
This:What you talking about.....
I really don't want to sound mean and I appreciate all you do for the community but telling the error is in SM64s sources is just wrong. The problem was outdated WUT from the beginning and you removing theThe error message saisKPADShutdown()
couldn't be found so you need to update WUT by compiling it for youself as this function has been added at the fourth of February 2022 while latest WUT release is from the first of November 2021.
KPADShutdown()
call from SM64s sources is just backporting it / masking the problem with invalid API usage.I believe, you were a bit toxic with your comments to me, and calm down my friend....@Fladulator Wait, you cloned the git repo to opt/devkitro/wut ? So tar tries to install it into the folder its coming from which seems to create an endless loop. Clone the repo to some other folder instead.
This:
I really don't want to sound mean and I appreciate all you do for the community but telling the error is in SM64s sources is just wrong. The problem was outdated WUT from the beginning and you removing theKPADShutdown()
call from SM64s sources is just backporting it / masking the problem with invalid API usage.
So backported instead of fixed, right?it's just the previous version
@Fladulator Wait, you cloned the git repo to opt/devkitro/wut ? So tar tries to install it into the folder its coming from which seems to create an endless loop. Clone the repo to some other folder instead.
Sorry to say but your opt/devkitpro folder is probably corrupted beyond repair, so the best way might be to just delete everything and start over from scratch.Hmmm did, but seems to do the same thing now.
git clone
to new/empty folders only. The folder from the git clone command I gave above is needed temporarily only (it's save to delete it after executing make install
). Also keep in mind that this temporary folder should not be the folder you want to install wut to.When you look close at your screenshot you see that theBtw. this message only pops up if I want to close msys2.
make install
command did not finish. All msys2 tells you in that message is exactly that: The command is still running so you should not close it.So I arrived home and it's still at the same screenWhen you look close at your screenshot you see that themake install
command did not finish. All msys2 tells you in that message is exactly that: The command is still running so you should not close it.
Hi @Fladulator ,So I arrived home and it's still at the same screen
Since I know a little more than yesterday I will try it by tomorrow from scratch. That's ok So You say I have to deinstall msys2 and install DEVKITPRO and then reinstall msys2 + repeat the steps from the tutorial to receive all the files needed?
I will post the new status quo tomorrow then.
Thank you guys very much!
@CrisMod
Are those glitchy texts in the German version gone in the newer version? Do you know sth about that?
Best,
TuF
KPADShutdown()
function. And from my part, reading now, that's what the other V10lator user was trying to tell you yesterday.git clone
in Terminal), since the master source files are in working-progress before releasing another beta or definitive version of the WUT libraries.WUT 1.0.0_beta12-1
which DID NOT include the KPADShutdown()
function. And that's why you should install yourself manually WUT in Working progress, if you want to test around and for your information only (till will not come out a WUT new version).devkitProUpdater-3.0.3 .exe
run it and let the software do the settings automatically for you. The software will do everything by itself, you don't have to put any key or set the environmental variables (always check that it has set it automatically).C:\devkitPro\msys2
.pacman -Sy
then pacman -Syu
.pacman -S wiiu-dev
and then continue with the installation of the libraries required by AboodXD for the compilation of SM64.pacman -Sl
function.make install
does: https://github.com/devkitPro/wut/blob/master/Makefile#L110-L112mkdir -p $(DESTDIR)$(DEVKITPRO)/wut
. You already have that path so that's unimportant. Let's jump directly to the next line: bzip2 -cd wut-$(VERSION).tar.bz2 | tar -xf - -C $(DESTDIR)$(DEVKITPRO)/wut
- so there must be a tar.bz2 file. Do you see it? Good. First let's try to use a better command to extract: tar xjf wut-*.tar.bz2 -C /path/to/devktipro/wut
(remember to replace "/path/to/devktipro" with the real path. No need to exchange anything else through).cp -ar include /path/to/devktipro/wut/
cp -ar lib /path/to/devktipro/wut/
cp -ar share /path/to/devktipro/wut/
Man, I really need your help. I read the tutorial from the discord + additional posts (since parts of the tut seems outdated). I also read the whole 20 pages of this thread even if I just understood half of what you guys say since I never had anything to do with compiling before...
It doesn't matter what I try I will always get this error message:
View attachment 310781
It doesn't matter if I try to compile the sm64ex version which I totally prefer or the sm64-port. I didn't forget the environmental variables or anything else which was mentioned. I googled the "KPADShutdown" error and found "a solution" which I am totally not able to achieve:
View attachment 310782
When I try to install wut via the commandmake install
it won't do the job and just gives me an error message. When I try updating it via the commandpacman -S wut-msys2
it just gives me two error messages saying
error: failed retrieving file 'wiiu-fling.db' from wii.leseratte10.de : The requested URL returned error: 404
error: failed to synchronize all databases (unexpected error)
--> I started with
[wiiu-fling]
Server = https://fling.heyquark.com
but found out in the thread that this page is outdated. By visiting the site it clearly stated that the waybackmachine link still stores the files so I changed https://fling.heyquark.com to https://web.archive.org/web/20200705125529/https://fling.heyquark.com/. This way I received the files needed for that period. Since Wling isn't needed anymore, I chose to ignore it. But trying to figure out how the KPAD error could be solved makes me dying right now... In the end it doesn't matter if I try updating wut-tools using different commands, I always end up here:
warning: wut-tools-1.3.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
MSYS2 just tells me that wut or wut-tools is up to date. The official GitHub pages tell me otherwise. I don't know how to solve this problem. I donwloaded wut-tools-1.3.2 but I don't know how to install it manually. And it makes me crazy seeing so many other people achieving it without any stress while I'm sitting here losing my mind Man, it was a piece of cake compiling a pc version for testing purpose. Please, can anyone of you, @AboodXD or anyone else, help me with an up-to-date tutorial or just help me solving this KPADShutdown problem? It would be great! I just want to play this freaking awesome port on my WiiU...
Thank you very much in advance!
Best,
TuF
extern "C" void KPADShutdown();
(I'll explain further on this when I am on my PC again so that I can post screenshots as well.)As for installing WUT from source code, don't worry about "make install" not working. It does not work for me either. You should just copy the "include" and "lib" files to the "opt" folder of wherever you have devkitPro (should be in the msys2 folder if you followed the tutorial to get devkitPro too).
it won't be uploaded since it contains assets from the actual game. you have to compile it yourself.Let me know when there's a compiled build available.
Hi @Fladulator ,
I try to help you, in concise and simple way.
[...]
My advise on what you can do now are:
1) For now, you have a working sm64-port version that the whole community played perfectly "until yesterday", and that is not that old version but is the older version than the one you can't compile now. So the new fixes, I don't think they can be so striking as to change your gaming experience.
2) Delete everything related to the Wii U environment on your PC, including the settings of MSYS2 / Mingw64 and environmental variables; because, reading your previous posts I believe that when you getting informing around (and you were good at it) by assimilating a lot of information in a short time, you made confusion between the compilation settings for SM64-Wii U and SM64-PC version which in the simplest way are set separately (you can set up all in one like I did, but you have to manually set multiple configurations).
3) Once everything is deleted, restart your PC and start to setting up again the Wii-U environment for Windows by going here: https://github.com/devkitPro/installer/releases , once downloadeddevkitProUpdater-3.0.3 .exe
run it and let the software do the settings automatically for you. The software will do everything by itself, you don't have to put any key or set the environmental variables (always check that it has set it automatically).
4) You will find your new Mingw64/32 in the following addressC:\devkitPro\msys2
.
5) Once everything is installed and Mingw64 opened, typepacman -Sy
thenpacman -Syu
.
6) Then, always remaining in Mingw64, download all the libraries necessary to start to set the compiler, withpacman -S wiiu-dev
and then continue with the installation of the libraries required by AboodXD for the compilation of SM64.
7) Check that you have all the libraries installed via thepacman -Sl
function.
[...]
pacman -Sy
pacman -Syu
pacman -S wiiu-dev
pacman -Sl
--> a few listed files were marked as [installed]pacman -S wiiu-dev wiiu-sdl2 git make python3 mingw-w64-x86_64-gcc --noconfirm
wut-tools is not wut! So try the following:
The first command will copy latest wut sources from github to your PC. Second command will switch into the directory the first one created an the other two are hopefully familiar already.Code:git clone https://github.com/devkitPro/wut.git cd wut make make install
BTW: The issue on the picture is: "no makefile found", so whatever you have there in the wut-tools folder isn't meaned to be compiled with make.
//EDIT:
No! The problem is outdated WUT. You're just masking the problem but not fix it.
git clone https://github.com/devkitPro/wut.git
cd wut
make
make install
cd /c/devkitPro/WiiU
git clone https://github.com/aboood40091/sm64-port.git
git clone https://github.com/aboood40091/sm64ex
cd sm64-port
make VERSION=eu