Hacking Noob-Proof guide to compile RxTools source.

  • Thread starter Thread starter capito27
  • Start date Start date
  • Views Views 23,808
  • Replies Replies 132
  • Likes Likes 18
Swap it should be c:\MinGW\bin;.... ;c:\devkitPro\msys\bin;:\Program Files\ImageMagick;C:\Program Files (x86)\Git\cmd. Mostly likely not the exact order since i don't have your exact path here... But MinGw should be first, then all the dedvkitpro stuff and then the imagemagick stuff.
Tried that and got the exact same output
 
huh. Just deleted my rxtools folder and did it from scratch again just to make sure (starting with "git clone --recursive https://github.com/roxas75/rxTools.git) and I didn't have to take any extra steps this time as far as building the cfwtool.exe and the other stuff in /tools/toolsrc. Just typed make, then make release. No issues at all.
 
Look in rxTools/tools. How many .exe files are there? There should be the same number as there are folders in rxTools/tools/toolsrc. If not, build all of them seperately and move the .exe files to rxTools/tools.
There are 4 .exe files. The one missing is xor.
How do you build this one separately?
 
There are 4 .exe files. The one missing is xor.
How do you build this one separately?
grab the build.bat from cfwtool and paste it into the xor folder. then edit the file so all 3 references to cfwtool.exe say xor.exe. But as I just tested from scratch again, you really shouldn't have to do that. Here is what is in my path and in this order:
C:\Program Files\ImageMagick-6.9.1-Q16;C:\Python27\;C:\Python27\Scripts;C:\mingw\msys\1.0\bin;D:\GnuWin32\bin;X:\devkitPro\msys\bin;x:\devkitPro\devkitARM\bin;C:\mingw\mingw32\bin;C:\mingw\bin;C:\mingw\libexec\gcc\mingw32\4.8.1;

Your error seems like is can't find arm-none-eabi-as. do you have a folder: \devkitPro\devkitARM\arm-none-eabi?

I suggest you try running the latest devkitPro installer again and do a full install. Just to it in the same place you have it now.

Edit: just noticed the extra ImageMagick entry in my path... that's because I initially grabbed the mingw binary .zip file before running into problems and realizing that there was a windows installer for it. I'm pretty sure it's not needed, but that's exactly what my path is right now. I started throwing everything I could in my path while figuring this thing out!
 
Last edited by urherenow,
grab the build.bat from cfwtool and paste it into the xor folder. then edit the file so all 3 references to cfwtool.exe say xor.exe. But as I just tested from scratch again, you really shouldn't have to do that. Here is what is in my path and in this order:
C:\Program Files\ImageMagick-6.9.1-Q16;C:\Python27\;C:\Python27\Scripts;C:\mingw\msys\1.0\bin;D:\GnuWin32\bin;X:\devkitPro\msys\bin;x:\devkitPro\devkitARM\bin;C:\mingw\mingw32\bin;C:\mingw\bin;C:\mingw\libexec\gcc\mingw32\4.8.1;C:\mingw\ImageMagick-6.8.5\bin;

Your error seems like is can't find arm-none-eabi-as. do you have a folder: \devkitPro\devkitARM\arm-none-eabi?

I suggest you try running the latest devkitPro installer again and do a full install. Just to it in the same place you have it now.

OK Two things:

1- Adding "c:\devkitPro\devkitARM\bin;" to the Path after "c:\devkitPro\msys\bin;" certainly helped. The make succeeded w/o any errors. However, no XOR.EXE was made in rxTools/tools.
2- I didn't know I had to do "Make release" after "Make". That solved it. I got an rxTools.dat created in G:\rxtools. 1MB in size.

I'll redo it again and get the separate outputs for each and post them.

Thanks for your help

EDIT: Here are the two output files (Make and Make release)
 

Attachments

Last edited by Pacman`,
OK Two things:

1- Adding "c:\devkitPro\devkitARM\bin;" to the Path after "c:\devkitPro\msys\bin;" certainly helped. The make succeeded w/o any errors. However, no XOR.EXE was made in rxTools/tools.
2- I didn't know I had to do "Make release" after "Make". That solved it. I got an rxTools.dat created in G:\rxtools. 1MB in size.

I'll redo it again and get the separate outputs for each and post them.

Thanks for your help
make release generates everything else in the release folder, like the ninjhax folder with the .3dsx and .smdh file.

Edit: Just re-checked myself and my fresh build doesn't seem to have generated the xor.exe either. Perhaps it isn't needed at all.

Edit2: Holy, crap! There's also a couple of .PDF files in there and apparently you also need to do a "make theme" for the latest version.

Never mind... make release covers what's done with "make theme", I think.
 
Last edited by urherenow,
make release generates everything else in the release folder, like the ninjhax folder with the .3dsx and .smdh file.

Edit: Just re-checked myself and my fresh build doesn't seem to have generated the xor.exe either. Perhaps it isn't needed at all.
Thank you for your help.
Without it, I would have been helpless
 
Being that we're on page 3 of a "noob-proof" guide, and most of it is errors people have come across, I'd be hard pressed to call this noob-proof :)
 
@capito27:

Thanks for your guide.
Could you add a few more things to it:

0- Disregard Point 1 from OP: 1. First of all, you'll want to grab a copy of the latest RxTools source code.
Instead, do 2- below, and use the git folder C:\rxTools instead

1- Path should have this at the beginning: c:\MinGW\bin;c:\devkitPro\msys\bin;c:\devkitPro\devkitARM\bin;C:\Program Files\ImageMagick; <-- your ImageMagick dir could be different (I didn't use the version number on mine)

2- just install https://git-scm.com/download/win
choice git for cmd command when install
then : git clone --recursive https://github.com/roxas75/rxTools.git
(thanks to Spzjulien)


3- After you do "Make", do "Make release" to get the rest of the release (thanks to urherenow)

This should make it work for everybody now :P

EDIT: I forgot to mention this, use the git folder created on root of C: (ie, rxTools)
instead of the folder rxTools-master. It's more complete.
 
Last edited by Pacman`,
Latest build works perfectly. Seriously thought there were more issues because I was a complete idiot and tried testing it out on an N3DS :facepalm:

So as of now, there are only 2 reasons to use a Gateway on an O3DS: For some reason you really want to stick with .3ds format stuff, and the region free patch still does nothing for out-of-region DLC (except with a GW).
 
I got past a few errors already, but now I'm a bit stuck. I'm coming up with this error:

Code:
make[1]: Entering directory `/c/GitRepos/rxTools/rxtools'
linking rxtools.elf
built ... rxtools.bin
make[1]: Leaving directory `/c/GitRepos/rxTools/rxtools'
0+1 records in
1+0 records out
917504 bytes (918 kB) copied, 0.001 seconds, 918 MB/s
make[1]: Entering directory `/c/GitRepos/rxTools/rxmode'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/c/GitRepos/rxTools/rxmode'
make[1]: Entering directory `/c/GitRepos/rxTools/rxmode'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/c/GitRepos/rxTools/rxmode'
make[1]: Entering directory `/c/GitRepos/rxTools/rxmode'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/c/GitRepos/rxTools/rxmode'
/bin/sh: python: command not found
make[1]: Entering directory `/c/GitRepos/rxTools/CakeHax'
arm-none-eabi-as -mcpu=mpcore -mlittle-endian  -o build/mset_4x/arm11_tools.o so
urce/arm11_tools.s
make[1]: arm-none-eabi-as: Command not found
make[1]: *** [build/mset_4x/arm11_tools.o] Error 127
make[1]: Leaving directory `/c/GitRepos/rxTools/CakeHax'
make: *** [rxTools.dat] Error 2

Any advice?
 
Yes. There are only 3 pages here. Read through all 3 and make sure your path is setup correctly. The path that paceman posted above is missing 2 Python27 directories...
 
Yes. There are only 3 pages here. Read through all 3 and make sure your path is setup correctly.
Believe me, I've read them all already. None of the rest of them seem to have the listed error.

Here's my paths though, if you'd like to look them over.

Code:
PATH=C:\ProgramData\Oracle\Java\javapath;"C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common";c:\devkitPro\msys\bin;"C:\Program Files (x86)\AMD APP\bin\x86_64";"C:\Program Files (x86)\AMD APP\bin\x86";C:\Windows\system32;C:\Windows\;C:\Windows\System32\Wbem;"C:\Windows\System32\WindowsPowerShell\v1.0\";"C:\Program Files (x86)\AMD\ATI.ACE\Core-Static";"C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\";"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\";"C:\Program Files\Microsoft SQL Server\100\DTS\Binn\";"C:\Program Files (x86)\WinSCP\";"C:\Program Files (x86)\Skype\Phone\";"C:\Program Files (x86)\GtkSharp\2.12\bin";"C:\Program Files\Prio";"C:\Program Files (x86)\Skype\Phone\";"C:\Program Files (x86)\AMD\ATI.ACE\Core-Static";"C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q2\bin";"C:\MinGW\msys\1.0\bin\";"C:\MinGW\bin";"C:\Python27";"C:\devkitPro\msys\bin";"C:\Program Files\ImageMagick-6.9.1-Q16";"C:\Program Files\mingw-w64\x86_64-5.1.0-win32-seh-rt_v4-rev0\mingw64\bin";

I even went through them and double-quoted everything, just in case.
 
Place your MinGW paths BEFORE your devkitPro paths.

Edit: you have too many MinGW installations going on there. Place c:/MinGW/bin and c:/MinGW/msys/1.0/bin before your devkitPro path (hint: you have it in your path TWICE and the first one is early on...), and add c:/Python27/Scripts and c:\devkitPro\devkitARM\bin.

Edit2: Also, my brain might be scrambled (been using different computers and OS's since the Commodore Vic-20) but some of those installations might not like it very much if your path is too long. You should place them at the beginning of your path.

Last edit: Ok, been replying from work off of memory, but the exact path I am using is a couple of posts above: https://gbatemp.net/threads/noob-proof-guide-to-compile-rxtools-source.392242/page-3#post-5570397

read that post and get your mingw/msys/1.0/bin before devkitpro and you should be fine. Or you may have to add that libexec folder as well. Let me know if you do need it...
The gnuwin32 folder is where I put my gnu make.exe file with the .dlls that it requires.
 
Last edited by urherenow,
Place your MinGW paths BEFORE your devkitPro paths.

Edit: you have too many MinGW installations going on there. Place c:/MinGW/bin and c:/MinGW/msys/1.0/bin before your devkitPro path (hint: you have it in your path TWICE and the first one is early on...), and add c:/Python27/Scripts and c:\devkitPro\devkitARM\bin.

Edit2: Also, my brain might be scrambled (been using different computers and OS's since the Commodore Vic-20) but some of those installations might not like it very much if your path is too long. You should place them at the beginning of your path.

Last edit: Ok, been replying from work off of memory, but the exact path I am using is a couple of posts above: https://gbatemp.net/threads/noob-proof-guide-to-compile-rxtools-source.392242/page-3#post-5570397

read that post and get your mingw/msys/1.0/bin before devkitpro and you should be fine. Or you may have to add that libexec folder as well. Let me know if you do need it...
The gnuwin32 folder is where I put my gnu make.exe file with the .dlls that it requires.
The first devkitpro path is under System PATH, not User PATH. I'll try removing it from System PATH. I installed MinGW-x86-64 on top of MinGW as it wasn't working originally. Also grabbed the GCC-ARM toolset as it appeared to be having trouble finding proper arm-none-eabi tools. As for GNUWin32, it's inaccessible right now, as SF is down. If you have a backup, it would be much appreciated if you could upload it somewhere for me, ha ha.

Anyway, I'm going to try a few things and see what happens. Thanks for taking the time to look this over.

Cleaned up PATH a bunch, rebooted, and lo-and-behold, a stack-dump trace. As GnuWin32 is inaccessible, I guess I'm SOL for now.
Shit, MSYS2 also grabs a bunch of resources from SF, can't use that either. I guess I really am SOL until SF comes back online.
 
Last edited by Gadorach,
You need to start from scratch and use my path already. The arm-none crap is in the devkitARM/bin directory, which is not in your path.
 
You need to start from scratch and use my path already. The arm-none crap is in the devkitARM/bin directory, which is not in your path.
It is, after modifications. I've been getting stack-dump crashes, but I can't get MSYS2 or GnuWin32 as SourceForge is offline for the required resources. It's not a path problem now, it's a resource problem. If you have a copy of the GnuWin32 install package, I'd appreciate it if you could upload it.

Oh, and here's my current path output.

Code:
PATH=C:\Windows\system32;C:\Windows\;C:\Windows\System32\Wbem;"C:\Windows\System32\WindowsPowerShell\v1.0\";"C:\Program Files (x86)\GtkSharp\2.12\bin";"C:\Program Files\Prio";C:\MinGW\msys\1.0\bin;C:\MinGW\bin;C:\devkitPro\msys\bin;C:\devkitPro\devkitARM\bin;C:\Python27;C:\Python27\Scripts;"C:\Program Files\ImageMagick-6.9.1-Q16"
 
Last edited by Gadorach,

Site & Scene News

Popular threads in this forum