Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

  • Thread starter Thread starter Roxas75
  • Start date Start date
  • Views Views 3,306,488
  • Replies Replies 19,240
  • Likes Likes 151
Status
Not open for further replies.
MinGW needs to be reordered so it's first in your path. Your Path looks to be missing some needed paths as well.

Here's what mine looks like: (everything after ImageMagick is windows related and not relevent to our dev environment)

Code:
C:\MinGW\bin;c:\devkitPro\msys\bin;C:\devkitPro\devkitARM\bin\;C:\devkitPro\devkitARM\arm-none-eabi\bin\;C:\Python27\;C:\Program Files (x86)\ImageMagick-6.9.1-Q16

That's how my path is setup and rxTools compiles fine for me. Also you may need to restart your computer before changes to PATH string work correctly.
 
Compiling source for me crashes attempting to build msethax.

error: 'readFirmware' was not declared in this scope
readFirmware(0,workbuffer,42);
^
d:/Downloads/rxTools-master_2/rxTools-master/msethax/rxinstaller/source/main.cpp
error: 'writeFirmware' was not declared in this scope
int ret = writeFirmware(userSettingsOffset,workbuffer,512);
^
make[3]: *** [main.o] Error 1
rm drunkenlogo.s
make[2]: *** [build] Error 2
make[2]: Leaving directory `/d/Downloads/rxTools-master_2/rxTools-master/msethax
/rxinstaller'
 
MinGW needs to be reordered so it's first in your path. Here's what mine looks like:
Actually devkitARM path is no more needed since all makefiles now have a DEVKITARM variable check :)

@gunner007
you forgot libnds
Get devkitPRO downloader and install devkitARM with all suboptions. THIS IS LISTED IN Readme.md!
 
Compiling source for me crashes attempting to build msethax.

error: 'readFirmware' was not declared in this scope
readFirmware(0,workbuffer,42);
^
d:/Downloads/rxTools-master_2/rxTools-master/msethax/rxinstaller/source/main.cpp
error: 'writeFirmware' was not declared in this scope
int ret = writeFirmware(userSettingsOffset,workbuffer,512);
^
make[3]: *** [main.o] Error 1
rm drunkenlogo.s
make[2]: *** [build] Error 2
make[2]: Leaving directory `/d/Downloads/rxTools-master_2/rxTools-master/msethax
/rxinstaller'

I had this issue, it's caused by an outdated libnds. Uninstall and then reinstall devkitARM, and make sure you have libnds checked in the installer.
 
anyone knows how to fix this error while compiling ?
Code:
D:\rxTools-master>make
make[1]: Entering directory `/d/rxTools-master/rxtools'
make[1]: ../tools/font_tool: Command not found
make[1]: *** [font.dat] Error 127
make[1]: Leaving directory `/d/rxTools-master/rxtools'
make: *** [rxtools/rxtools.bin] Error 2

D:\rxTools-master>
 
Actually devkitARM path is no more needed since all makefiles now have a DEVKITARM variable check :)
EDIT: Tried to compile without the path set, it asked me to set the path.
so i set the path, and it worked then
 
anyone knows how to fix this error while compiling ?
Code:
D:\rxTools-master>make
make[1]: Entering directory `/d/rxTools-master/rxtools'
make[1]: ../tools/font_tool: Command not found
make[1]: *** [font.dat] Error 127
make[1]: Leaving directory `/d/rxTools-master/rxtools'
make: *** [rxtools/rxtools.bin] Error 2

D:\rxTools-master>

That particular commit is missing the font_tool directory/what belongs in it, I believe. Not every commit is gonna compile.
 
fd4d385d3e.png

Bumped MinGW to the top, caught some errors but then it goes through the whole process shown in my gif and stops at the same place, trying to open some .elf. This happens even if I empty the folder and give it a clean source from the git.
 
ok I got rxtools to compile finally !
It seems the error i was getting was because of an outdated source i was using. (24hrs outdated).

Thank you everyone who helped me :)
 
  • Like
Reactions: coolfuze
fd4d385d3e.png

Bumped MinGW to the top, caught some errors but then it goes through the whole process shown in my gif and stops at the same place, trying to open some .elf. This happens even if I empty the folder and give it a clean source from the git.

Dumb as it sounds, [.exe is actually part of MSYS. Make sure your MinGW/msys/1.0/bin/ directory is on your Path.
 
Uninstalled everything, restarted, reinstalled, deleted and re extracted a clean release source, ran as admin, still hangs at the same .elf bit..

I was! I completely missed the arm-none-eabi\bin post. Still hangs though.

Dumb as it sounds, [.exe is actually part of MSYS. Make sure your MinGW/msys/1.0/bin/ directory is on your Path.

Yup, it's there.
64b0e452e5.png

Then %DEVKITPRO% and %DEVKITARM% are set independently, but it still doesn't work.

What are the exact steps I need to follow to get this to function if I uninstall everything except VB and Python (which i had installed prior anyway)?
 
Last edited by Rhymekaze,
Yup, it's there.

It's not there. Just because the path is similar doesn't mean it's the right folder. Go find out where your MingW is actually installed. Check msys/bin in that dir. Does it have all the binaries needed(rm, [, cp etc)? That's the one you want in your path.
 
Supposed to do anything with the theme folder? Compiled rxtool.dat succesfully, but just hangs at the moment booting through mset.
 
Supposed to do anything with the theme folder? Compiled rxtool.dat succesfully, but just hangs at the moment booting through mset.

If you have the latest revision: You need ImageMagick, specifically convert.exe and delegates.txt (and the DLLs if you use the dll version). Put all of those in the "theme" directory in the source folder alongside all the images, then run make in the theme folder. Take all the .bin files you get, and copy them to your SD card under rxTools/Theme/0/. That's the procedure right now, at least.

The reason make doesn't fail WITHOUT the ImageMagick files in the folder is because Windows has a "convert.exe" of its own (totally different), and it gets used if you don't have imagemagick's convert.exe in the directory, so it fails silently.

To the devs: I read over ImageMagick's license. It's legal for you to include convert.exe (with proper attribution), is it not? Would probably be a good idea to avoid the confusion of silently failed builds.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum